Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2de14b4325af3a969d662eac1d70b9bf45c2aa9428437dfd18e44656f1f2e49d

Tx prefix hash: ad1a6b1c8969eee01cf9b0364812dd55495103f03d9579f5bdd209dc6b535f07
Tx public key: 3ae94dea6516bbfbe4a55ca53848ce9560643eb1226dc939ab27e5df10e098b2
Timestamp: 1750905454 Timestamp [UCT]: 2025-06-26 02:37:34 Age [y:d:h:m:s]: 00:147:16:18:03
Block: 1312900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103527 RingCT/type: yes/0
Extra: 013ae94dea6516bbfbe4a55ca53848ce9560643eb1226dc939ab27e5df10e098b202110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 643597e2a0be41a7722b3e615c2d3871fb86fe6a4835363d8925fec3fd2839e6 0.600000000000 1800537 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": 1312910, "vin": [ { "gen": { "height": 1312900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "643597e2a0be41a7722b3e615c2d3871fb86fe6a4835363d8925fec3fd2839e6" } } ], "extra": [ 1, 58, 233, 77, 234, 101, 22, 187, 251, 228, 165, 92, 165, 56, 72, 206, 149, 96, 100, 62, 177, 34, 109, 201, 57, 171, 39, 229, 223, 16, 224, 152, 178, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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