Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65006c12e3d3a25131ccb7c9840a0beadc6cf3078fa6fbf9993c63bd13ddbfaf

Tx prefix hash: 66d661a15070d7ecfd22fef4540a7e8e71ebe244d159a08e550a429e8143a9e4
Tx public key: 8551386d26827cced04ab05eba48e5b59a6cae415a1b3d991563504b7abf74df
Timestamp: 1745596732 Timestamp [UCT]: 2025-04-25 15:58:52 Age [y:d:h:m:s]: 00:210:08:27:49
Block: 1269253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148054 RingCT/type: yes/0
Extra: 018551386d26827cced04ab05eba48e5b59a6cae415a1b3d991563504b7abf74df021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65f179bff7e453de7208a021d9c03010b3e2a5e134484033c0e6578399202d8f 0.600000000000 1756488 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": 1269263, "vin": [ { "gen": { "height": 1269253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65f179bff7e453de7208a021d9c03010b3e2a5e134484033c0e6578399202d8f" } } ], "extra": [ 1, 133, 81, 56, 109, 38, 130, 124, 206, 208, 74, 176, 94, 186, 72, 229, 181, 154, 108, 174, 65, 90, 27, 61, 153, 21, 99, 80, 75, 122, 191, 116, 223, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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