Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4aa24ec02b39a1edf9e703476e748f6f8b4fb13ae28a9e9bb9250d1b6c50dd9d

Tx prefix hash: 30a684bb5d52a90eff60c593d5e3a2e0abcc5534506490289602f02e91e11c17
Tx public key: b868f37dafe8e72459ef3c20fdfa032154b24cc8ca19cd34c773f11722afa95d
Timestamp: 1582097963 Timestamp [UCT]: 2020-02-19 07:39:23 Age [y:d:h:m:s]: 04:321:20:25:50
Block: 67905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122582 RingCT/type: yes/0
Extra: 01b868f37dafe8e72459ef3c20fdfa032154b24cc8ca19cd34c773f11722afa95d021100000001026b59f3000000000000000000

1 output(s) for total of 365.597614259000 dcy

stealth address amount amount idx
00: 009ef09b3950e56ba70203672c121724503c2fe872284d61d4d28ebfa2d695f1 365.597614259000 125117 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 67915, "vin": [ { "gen": { "height": 67905 } } ], "vout": [ { "amount": 365597614259, "target": { "key": "009ef09b3950e56ba70203672c121724503c2fe872284d61d4d28ebfa2d695f1" } } ], "extra": [ 1, 184, 104, 243, 125, 175, 232, 231, 36, 89, 239, 60, 32, 253, 250, 3, 33, 84, 178, 76, 200, 202, 25, 205, 52, 199, 115, 241, 23, 34, 175, 169, 93, 2, 17, 0, 0, 0, 1, 2, 107, 89, 243, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8