Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5946ef553433d1b835346b34f1b03988f72fcb36a77b3bfa70ece920be743a7

Tx prefix hash: f2a12a954655029259e747e3156f901a7a4fa845a4f34b00d006664628594e71
Tx public key: 9a19701d1fc58ebe7c1c0ab844a95b20712f0ee89a8c3aa279510453dd37dc8e
Timestamp: 1736762706 Timestamp [UCT]: 2025-01-13 10:05:06 Age [y:d:h:m:s]: 00:063:15:06:18
Block: 1196392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45252 RingCT/type: yes/0
Extra: 019a19701d1fc58ebe7c1c0ab844a95b20712f0ee89a8c3aa279510453dd37dc8e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d23d972f1d05641e3a61ab45cee89605e4ad7817b5d565e62a9d0d2b4338207b 0.600000000000 1682991 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": 1196402, "vin": [ { "gen": { "height": 1196392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d23d972f1d05641e3a61ab45cee89605e4ad7817b5d565e62a9d0d2b4338207b" } } ], "extra": [ 1, 154, 25, 112, 29, 31, 197, 142, 190, 124, 28, 10, 184, 68, 169, 91, 32, 113, 47, 14, 232, 154, 140, 58, 162, 121, 81, 4, 83, 221, 55, 220, 142, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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