Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 341e2fcea91818aa8f0b11683acba99b852666fa636576210950889a28f91f2a

Tx prefix hash: fbcbdbb1f5891565fd744f3e2b02dd17a6959db8f857d0f4a27b33e1644913b6
Tx public key: 8eacefd7fb85ad786b3b21cc32e7f45293a1ce9c21f71d01a3039df8ace9647f
Timestamp: 1761978930 Timestamp [UCT]: 2025-11-01 06:35:30 Age [y:d:h:m:s]: 00:013:02:15:00
Block: 1402486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9354 RingCT/type: yes/0
Extra: 018eacefd7fb85ad786b3b21cc32e7f45293a1ce9c21f71d01a3039df8ace9647f02110000000cdf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c79736d3b504b16cc08849053004504e1268c2f09ae72f8e4f8e0c26a30084a1 0.600000000000 1890805 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": 1402496, "vin": [ { "gen": { "height": 1402486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c79736d3b504b16cc08849053004504e1268c2f09ae72f8e4f8e0c26a30084a1" } } ], "extra": [ 1, 142, 172, 239, 215, 251, 133, 173, 120, 107, 59, 33, 204, 50, 231, 244, 82, 147, 161, 206, 156, 33, 247, 29, 1, 163, 3, 157, 248, 172, 233, 100, 127, 2, 17, 0, 0, 0, 12, 223, 90, 36, 122, 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