Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d42af385ec694b9ce7289785a305bc2d59d91975066f9c50ffbc2904cfee554a

Tx prefix hash: 803946ccdacc0c9f21b1668a590f0f2f4c45cb94e38c21bf4ada5849e00fbdf4
Tx public key: 60f82b3a9efe9c47464ec90ee16d9df992962c882e3d0ecb72e800d785da0f7f
Timestamp: 1741281258 Timestamp [UCT]: 2025-03-06 17:14:18 Age [y:d:h:m:s]: 00:006:00:06:07
Block: 1233529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4304 RingCT/type: yes/0
Extra: 0160f82b3a9efe9c47464ec90ee16d9df992962c882e3d0ecb72e800d785da0f7f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abf0c26cee0d136307941fee929cab539582aff199ed6a094ec1e9f933d6b9b2 0.600000000000 1720452 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": 1233539, "vin": [ { "gen": { "height": 1233529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abf0c26cee0d136307941fee929cab539582aff199ed6a094ec1e9f933d6b9b2" } } ], "extra": [ 1, 96, 248, 43, 58, 158, 254, 156, 71, 70, 78, 201, 14, 225, 109, 157, 249, 146, 150, 44, 136, 46, 61, 14, 203, 114, 232, 0, 215, 133, 218, 15, 127, 2, 17, 0, 0, 0, 3, 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