Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 216e21ec4d8448fe7fb50262ebc69378c0ba3324565849bb512a093494bdbe00

Tx prefix hash: 187791cb29223fcfa4ea1fe07f36cf0b15f19d3c8a5562eb861be263f4785e5c
Tx public key: c933e49d76db8d9ab9f15f18a0e6b2f991a1eeb114fec024389f06a4baafd0c8
Timestamp: 1760415124 Timestamp [UCT]: 2025-10-14 04:12:04 Age [y:d:h:m:s]: 00:032:22:16:06
Block: 1389505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23574 RingCT/type: yes/0
Extra: 01c933e49d76db8d9ab9f15f18a0e6b2f991a1eeb114fec024389f06a4baafd0c80211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6cd7938b21f2993a3f02d5369d45c24d869056184b88d740d2b3ca51b90f084 0.600000000000 1877734 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": 1389515, "vin": [ { "gen": { "height": 1389505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6cd7938b21f2993a3f02d5369d45c24d869056184b88d740d2b3ca51b90f084" } } ], "extra": [ 1, 201, 51, 228, 157, 118, 219, 141, 154, 185, 241, 95, 24, 160, 230, 178, 249, 145, 161, 238, 177, 20, 254, 192, 36, 56, 159, 6, 164, 186, 175, 208, 200, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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