Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b0b4ef6de7b57bc5b38e0e79b800cd33eb14395fe225a7b6619bc6a16199c70

Tx prefix hash: 31a2a3566a0b707914e007540c8d40d309e90963332e0f062fcdfc52b0cdcf32
Tx public key: d687ec8fb7410f020c05d60df96180cd0d00a444359d31150edcfe6ea5eaf5fe
Timestamp: 1681403821 Timestamp [UCT]: 2023-04-13 16:37:01 Age [y:d:h:m:s]: 01:273:20:05:41
Block: 737808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457218 RingCT/type: yes/0
Extra: 01d687ec8fb7410f020c05d60df96180cd0d00a444359d31150edcfe6ea5eaf5fe0211000000045029cbac000000000000000000

1 output(s) for total of 2.204681652000 dcy

stealth address amount amount idx
00: 44364a37d6e2895c2b29e026bdb2c1fd7cffe904d8163bdedf7aef96cbe28b95 2.204681652000 1184415 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": 737818, "vin": [ { "gen": { "height": 737808 } } ], "vout": [ { "amount": 2204681652, "target": { "key": "44364a37d6e2895c2b29e026bdb2c1fd7cffe904d8163bdedf7aef96cbe28b95" } } ], "extra": [ 1, 214, 135, 236, 143, 183, 65, 15, 2, 12, 5, 214, 13, 249, 97, 128, 205, 13, 0, 164, 68, 53, 157, 49, 21, 14, 220, 254, 110, 165, 234, 245, 254, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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