Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e22bb7ceded7b2d1d19dc09aeb10e4dd812bc0e050f2c1e5feb285d4f95ce9c

Tx prefix hash: 8f016c129976be64edbe52832de1fa85e478c395b3bc9154aead3b9516904169
Tx public key: 62cb323ac2d6fd1480e525a4d3d449fca90591bc60f0e1c01e7d0ef9eceb4548
Timestamp: 1731281951 Timestamp [UCT]: 2024-11-10 23:39:11 Age [y:d:h:m:s]: 00:144:23:30:26
Block: 1151005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103436 RingCT/type: yes/0
Extra: 0162cb323ac2d6fd1480e525a4d3d449fca90591bc60f0e1c01e7d0ef9eceb454802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7ec33b0ea0ec967bc5ef6ef5d2969d9e0e3599d6ca4ba7af641c9666a1102d1 0.600000000000 1636456 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": 1151015, "vin": [ { "gen": { "height": 1151005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7ec33b0ea0ec967bc5ef6ef5d2969d9e0e3599d6ca4ba7af641c9666a1102d1" } } ], "extra": [ 1, 98, 203, 50, 58, 194, 214, 253, 20, 128, 229, 37, 164, 211, 212, 73, 252, 169, 5, 145, 188, 96, 240, 225, 192, 30, 125, 14, 249, 236, 235, 69, 72, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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