Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96b6b6ff84339d760d194ea6e508477ea7639b59049db96941cc4cae724c38dc

Tx prefix hash: fa433bb4737594deadc3847ca962db73cb7a5f18ab45d66a6007f5783164d933
Tx public key: 3db4ff769cc92795861d0f4b46cc8dae28c8d0b66a51110c8e94cdaa6f924419
Timestamp: 1709125478 Timestamp [UCT]: 2024-02-28 13:04:38 Age [y:d:h:m:s]: 01:108:20:01:22
Block: 967409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338722 RingCT/type: yes/0
Extra: 013db4ff769cc92795861d0f4b46cc8dae28c8d0b66a51110c8e94cdaa6f9244190211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 223de3f35d79b29f85fe95007a4e3dfdc2651eeae478670320c30664b3851eb3 0.600000000000 1427188 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": 967419, "vin": [ { "gen": { "height": 967409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "223de3f35d79b29f85fe95007a4e3dfdc2651eeae478670320c30664b3851eb3" } } ], "extra": [ 1, 61, 180, 255, 118, 156, 201, 39, 149, 134, 29, 15, 75, 70, 204, 141, 174, 40, 200, 208, 182, 106, 81, 17, 12, 142, 148, 205, 170, 111, 146, 68, 25, 2, 17, 0, 0, 0, 4, 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