Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 025be1aed12b341092bcc0ca7fc87c0b4ac3731e4280f83df6359c90d09499dc

Tx prefix hash: fd06dc7dc4a333e261efb9ced97d746bbd4172fc2f962e1ffe61ec05d781ef06
Tx public key: e4c02c7768ffa7192f20fccb73a27e194f90ef0edce4e90d411072837db7d666
Timestamp: 1648894030 Timestamp [UCT]: 2022-04-02 10:07:10 Age [y:d:h:m:s]: 03:043:04:56:49
Block: 471566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 811261 RingCT/type: yes/0
Extra: 01e4c02c7768ffa7192f20fccb73a27e194f90ef0edce4e90d411072837db7d6660211000000122e6b1fd5000000000000000000

1 output(s) for total of 16.807624341000 dcy

stealth address amount amount idx
00: 280dbeb29732f1eb90d1f270462c057e0b7740d5c12078b10880c25270e25b31 16.807624341000 890922 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": 471576, "vin": [ { "gen": { "height": 471566 } } ], "vout": [ { "amount": 16807624341, "target": { "key": "280dbeb29732f1eb90d1f270462c057e0b7740d5c12078b10880c25270e25b31" } } ], "extra": [ 1, 228, 192, 44, 119, 104, 255, 167, 25, 47, 32, 252, 203, 115, 162, 126, 25, 79, 144, 239, 14, 220, 228, 233, 13, 65, 16, 114, 131, 125, 183, 214, 102, 2, 17, 0, 0, 0, 18, 46, 107, 31, 213, 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