Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b7cf5ec89b719140b2615b1c1f64eec9b86700eea75f2cdf0bcb2db3b697d4f

Tx prefix hash: 6c8a4e2bf8ffa9a706af57afaa546265509afa2525047aacabf22c2ce813db05
Tx public key: 476259f6af9fe3344a5a8dbd93cedf67d3b6740d6d2dea2c26cedf94532df7c2
Timestamp: 1694235747 Timestamp [UCT]: 2023-09-09 05:02:27 Age [y:d:h:m:s]: 01:138:06:18:01
Block: 844133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360109 RingCT/type: yes/0
Extra: 01476259f6af9fe3344a5a8dbd93cedf67d3b6740d6d2dea2c26cedf94532df7c202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.979573482000 dcy

stealth address amount amount idx
00: dd048c2a5c52c62e2dc36b883526bcbf8eee20b1b9b4c77869d22121f61f39ad 0.979573482000 1297421 of 0

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": 844143, "vin": [ { "gen": { "height": 844133 } } ], "vout": [ { "amount": 979573482, "target": { "key": "dd048c2a5c52c62e2dc36b883526bcbf8eee20b1b9b4c77869d22121f61f39ad" } } ], "extra": [ 1, 71, 98, 89, 246, 175, 159, 227, 52, 74, 90, 141, 189, 147, 206, 223, 103, 211, 182, 116, 13, 109, 45, 234, 44, 38, 206, 223, 148, 83, 45, 247, 194, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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