Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1b4d06f1e0f92e46abf966fd39574efa224632a208b1807cea18cb3d2bb4e63

Tx prefix hash: 4c2f5a1badef55d2cf389be0abd2d272e44d508e13d5666fc9befb25e411344a
Tx public key: c9f62f303f930d9567f49846c2e55be0584f4be469cebd438bd3afd5dd322345
Timestamp: 1734864261 Timestamp [UCT]: 2024-12-22 10:44:21 Age [y:d:h:m:s]: 00:177:06:55:16
Block: 1180700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126405 RingCT/type: yes/0
Extra: 01c9f62f303f930d9567f49846c2e55be0584f4be469cebd438bd3afd5dd3223450211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ab54045b33f0904edabade3609dbb38a68a1c67b099dc63cd981df84318e2db 0.600000000000 1667113 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": 1180710, "vin": [ { "gen": { "height": 1180700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ab54045b33f0904edabade3609dbb38a68a1c67b099dc63cd981df84318e2db" } } ], "extra": [ 1, 201, 246, 47, 48, 63, 147, 13, 149, 103, 244, 152, 70, 194, 229, 91, 224, 88, 79, 75, 228, 105, 206, 189, 67, 139, 211, 175, 213, 221, 50, 35, 69, 2, 17, 0, 0, 0, 7, 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