Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cf16409eb7a732023bd9c7bdc3a70e01ef098b397543a6fd0a3683119e853f2

Tx prefix hash: e8e8c2f18530e8cc9056815381fe431174a3d0bed0551b8069bccc84f371742e
Tx public key: 402411b13a462d6e609dedd62a8ff76832597ae68948c6cc556b8b8b5d7a5f9a
Timestamp: 1736614190 Timestamp [UCT]: 2025-01-11 16:49:50 Age [y:d:h:m:s]: 00:061:14:21:48
Block: 1195149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43806 RingCT/type: yes/0
Extra: 01402411b13a462d6e609dedd62a8ff76832597ae68948c6cc556b8b8b5d7a5f9a0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c924b4e45e7d90489e90c01a135e59cd4f764ba0b580bc9d083d3ceb0ce28b7 0.600000000000 1681738 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": 1195159, "vin": [ { "gen": { "height": 1195149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c924b4e45e7d90489e90c01a135e59cd4f764ba0b580bc9d083d3ceb0ce28b7" } } ], "extra": [ 1, 64, 36, 17, 177, 58, 70, 45, 110, 96, 157, 237, 214, 42, 143, 247, 104, 50, 89, 122, 230, 137, 72, 198, 204, 85, 107, 139, 139, 93, 122, 95, 154, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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