Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199885d3b3a022316641ec2744632865b9fc4698e2e1d8a3204a596f814916a1

Tx prefix hash: a619669e0e43d381f5daef1b87103934b7e261b1ed5c0664858b6085bdb47f4f
Tx public key: d717fa13b8c4a8b380703bf73552e5b7628f446c31a252898bc4e7d4eeac96df
Timestamp: 1751147325 Timestamp [UCT]: 2025-06-28 21:48:45 Age [y:d:h:m:s]: 00:140:15:39:26
Block: 1314778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98619 RingCT/type: yes/0
Extra: 01d717fa13b8c4a8b380703bf73552e5b7628f446c31a252898bc4e7d4eeac96df021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 132373f9456ec364418131e65dbf23824914eaaaebc2e38a1cf192cbcd0e3585 0.600000000000 1802429 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": 1314788, "vin": [ { "gen": { "height": 1314778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "132373f9456ec364418131e65dbf23824914eaaaebc2e38a1cf192cbcd0e3585" } } ], "extra": [ 1, 215, 23, 250, 19, 184, 196, 168, 179, 128, 112, 59, 247, 53, 82, 229, 183, 98, 143, 68, 108, 49, 162, 82, 137, 139, 196, 231, 212, 238, 172, 150, 223, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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