Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b0edc1efad63104c319f04607479d0e8d74aead364df5990b0c307ffc99db34

Tx prefix hash: 8e595bdf1983995eef1196401ea9042f010e04368b70a675fb891c45ae8dba2d
Tx public key: 40f0bc2cdabb4854c6e9a599fd36303fe744d7a47a53559ad0c78c7f37b26d0d
Timestamp: 1708464746 Timestamp [UCT]: 2024-02-20 21:32:26 Age [y:d:h:m:s]: 01:113:15:15:44
Block: 961917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342224 RingCT/type: yes/0
Extra: 0140f0bc2cdabb4854c6e9a599fd36303fe744d7a47a53559ad0c78c7f37b26d0d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c4bd7e5f3d531d7fbdd7dd7996f3a2fc53ed586569219bee3703837db65506d 0.600000000000 1421534 of 15

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": 961927, "vin": [ { "gen": { "height": 961917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c4bd7e5f3d531d7fbdd7dd7996f3a2fc53ed586569219bee3703837db65506d" } } ], "extra": [ 1, 64, 240, 188, 44, 218, 187, 72, 84, 198, 233, 165, 153, 253, 54, 48, 63, 231, 68, 215, 164, 122, 83, 85, 154, 208, 199, 140, 127, 55, 178, 109, 13, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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