Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6d454db6c100374f202f45fbcca29aefa86c992b9300c309478aa1f817d4ea1

Tx prefix hash: fc76280d18710966dc8d3e79bf6dedd5030beb8ce41aaa0d5dbf861191eb6189
Tx public key: 792136650a54ddb1ea4ee91ef2fd177db3acbef90a9f841f482449ab89e9df70
Timestamp: 1724454624 Timestamp [UCT]: 2024-08-23 23:10:24 Age [y:d:h:m:s]: 00:266:05:17:50
Block: 1094496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190150 RingCT/type: yes/0
Extra: 01792136650a54ddb1ea4ee91ef2fd177db3acbef90a9f841f482449ab89e9df7002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f8d2842e8899d34f0c3f53ee8045bd65e82750c337929d0b26a0f1eb264dc0e 0.600000000000 1569613 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": 1094506, "vin": [ { "gen": { "height": 1094496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f8d2842e8899d34f0c3f53ee8045bd65e82750c337929d0b26a0f1eb264dc0e" } } ], "extra": [ 1, 121, 33, 54, 101, 10, 84, 221, 177, 234, 78, 233, 30, 242, 253, 23, 125, 179, 172, 190, 249, 10, 159, 132, 31, 72, 36, 73, 171, 137, 233, 223, 112, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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