Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 976a061de622719d1b5253714961f155c6ef891deffb10aa9be5071bee6dc075

Tx prefix hash: aec41ffa0f306cdf60938333c30ec909ed7a6c5ad8c6cb3e454a17b3baf0e0ed
Tx public key: 167703d8d5d1fc2891bc5e3c9f23388374b1ef8d37ae21573dc83e8498eafd26
Timestamp: 1735809372 Timestamp [UCT]: 2025-01-02 09:16:12 Age [y:d:h:m:s]: 00:168:02:57:03
Block: 1188490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119844 RingCT/type: yes/0
Extra: 01167703d8d5d1fc2891bc5e3c9f23388374b1ef8d37ae21573dc83e8498eafd26021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39174501a988fbad2446e44e273a6d14be209a7a85de7902645d7ccd0ed68bff 0.600000000000 1674991 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": 1188500, "vin": [ { "gen": { "height": 1188490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39174501a988fbad2446e44e273a6d14be209a7a85de7902645d7ccd0ed68bff" } } ], "extra": [ 1, 22, 119, 3, 216, 213, 209, 252, 40, 145, 188, 94, 60, 159, 35, 56, 131, 116, 177, 239, 141, 55, 174, 33, 87, 61, 200, 62, 132, 152, 234, 253, 38, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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