Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24c86abaae8d48ae765297d64f23ab620550a1155e5f1ee693968f8ecb0eee19

Tx prefix hash: ae12a17e713775a1f25044bb02d4f0e9c74861cdae7a80904b1bfe10bb75a8fd
Tx public key: 00d37498562cee846acd50a23bf586631082c6fec319c980b4ecf5243ce3ac0a
Timestamp: 1726268111 Timestamp [UCT]: 2024-09-13 22:55:11 Age [y:d:h:m:s]: 00:132:06:03:31
Block: 1109519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94538 RingCT/type: yes/0
Extra: 0100d37498562cee846acd50a23bf586631082c6fec319c980b4ecf5243ce3ac0a021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f75281cb3c59bac21922e5e90b66a8d0e74cbbbff67abb30a0b2f4e006bdb2d1 0.600000000000 1587802 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": 1109529, "vin": [ { "gen": { "height": 1109519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f75281cb3c59bac21922e5e90b66a8d0e74cbbbff67abb30a0b2f4e006bdb2d1" } } ], "extra": [ 1, 0, 211, 116, 152, 86, 44, 238, 132, 106, 205, 80, 162, 59, 245, 134, 99, 16, 130, 198, 254, 195, 25, 201, 128, 180, 236, 245, 36, 60, 227, 172, 10, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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