Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4772f37689a1bbdfded0719b32670a00ef4a7de2383c048198851c2e4e85f1b2

Tx prefix hash: 26a52fd6d7717b02d16ed679667cc0fa649316c468c1e5482373a1b7f55ccee8
Tx public key: 5187abbbdeabec3ef5208833ce6b7d2516b4f44d9e8985c3d5cb11c13d4d46c8
Timestamp: 1703632574 Timestamp [UCT]: 2023-12-26 23:16:14 Age [y:d:h:m:s]: 01:101:05:30:15
Block: 921863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333463 RingCT/type: yes/0
Extra: 015187abbbdeabec3ef5208833ce6b7d2516b4f44d9e8985c3d5cb11c13d4d46c802110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e96dc70e0196944cb39c93d424ab669bec8c96399c31418c58e4f4facc477a6e 0.600000000000 1379557 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": 921873, "vin": [ { "gen": { "height": 921863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e96dc70e0196944cb39c93d424ab669bec8c96399c31418c58e4f4facc477a6e" } } ], "extra": [ 1, 81, 135, 171, 187, 222, 171, 236, 62, 245, 32, 136, 51, 206, 107, 125, 37, 22, 180, 244, 77, 158, 137, 133, 195, 213, 203, 17, 193, 61, 77, 70, 200, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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