Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 990a2ac03f95843881f2ec230acdb7378366be8ade04d4a52f5e6e915e36c785

Tx prefix hash: 65b45226c5a917d65998c644f95eecdb88745143f73a1b103a51bea76a13bf5a
Tx public key: fdbeb87e7d874a690e664be062c5dbb1a401272d5d03a3a92c248df4c5a45fca
Timestamp: 1704995605 Timestamp [UCT]: 2024-01-11 17:53:25 Age [y:d:h:m:s]: 01:000:03:17:47
Block: 933144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261426 RingCT/type: yes/0
Extra: 01fdbeb87e7d874a690e664be062c5dbb1a401272d5d03a3a92c248df4c5a45fca0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 266594e23c4bf5d2c9a68420c0141ba5e3f9985671397f3ba85d056e4a70856a 0.600000000000 1391100 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": 933154, "vin": [ { "gen": { "height": 933144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "266594e23c4bf5d2c9a68420c0141ba5e3f9985671397f3ba85d056e4a70856a" } } ], "extra": [ 1, 253, 190, 184, 126, 125, 135, 74, 105, 14, 102, 75, 224, 98, 197, 219, 177, 164, 1, 39, 45, 93, 3, 163, 169, 44, 36, 141, 244, 197, 164, 95, 202, 2, 17, 0, 0, 0, 9, 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