Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84cb0b10a97b9df04a127ac4adb23fabc17225d135a3c63d09fa23fb4f388f29

Tx prefix hash: 3c8c5d6b4960599d54095e188a635e158fbf6741bb7471117103286ff46f5db6
Tx public key: c7501af84e53c0e46ecd5d33d144ff0bf41898b53ffbcf14f20f2f34c7d0ba2d
Timestamp: 1710569296 Timestamp [UCT]: 2024-03-16 06:08:16 Age [y:d:h:m:s]: 01:003:05:30:41
Block: 979393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263282 RingCT/type: yes/0
Extra: 01c7501af84e53c0e46ecd5d33d144ff0bf41898b53ffbcf14f20f2f34c7d0ba2d0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f8244e7e45f54a4242a72c9879d19c8eef1a70fe858435e8243828fe2513868 0.600000000000 1439426 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": 979403, "vin": [ { "gen": { "height": 979393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f8244e7e45f54a4242a72c9879d19c8eef1a70fe858435e8243828fe2513868" } } ], "extra": [ 1, 199, 80, 26, 248, 78, 83, 192, 228, 110, 205, 93, 51, 209, 68, 255, 11, 244, 24, 152, 181, 63, 251, 207, 20, 242, 15, 47, 52, 199, 208, 186, 45, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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