Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f59503056e7d39af07490b02682f7d7ee6268f2179dfe64168be84bc198666e

Tx prefix hash: cdd5c2a9eff069c05367da0b49e97d55323a1d3056875b39841e0de2ff5b141a
Tx public key: 6a67e330fbc992d2c0cbc4f0d19047238a808a9b288447e3d92e561a4d39108c
Timestamp: 1728296716 Timestamp [UCT]: 2024-10-07 10:25:16 Age [y:d:h:m:s]: 00:193:09:35:59
Block: 1126337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138028 RingCT/type: yes/0
Extra: 016a67e330fbc992d2c0cbc4f0d19047238a808a9b288447e3d92e561a4d39108c02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f31ed6ae7efd0ad091eaf4b8c437e92654f004f8994ac2ec6f4b0dc2e3360041 0.600000000000 1609126 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": 1126347, "vin": [ { "gen": { "height": 1126337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f31ed6ae7efd0ad091eaf4b8c437e92654f004f8994ac2ec6f4b0dc2e3360041" } } ], "extra": [ 1, 106, 103, 227, 48, 251, 201, 146, 210, 192, 203, 196, 240, 209, 144, 71, 35, 138, 128, 138, 155, 40, 132, 71, 227, 217, 46, 86, 26, 77, 57, 16, 140, 2, 17, 0, 0, 0, 3, 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