Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: febe1191fd31eec5bf69903de3c40d283594dbc1b9c809b3cd1b4b9283404146

Tx prefix hash: 413568f55f64e2b2ebdc6d5281c309e65081432ef24a926487698a260a5e9f32
Tx public key: bee99f4119e788e8b76de250d9af930a7dd88e824f693d477947fa82f1d052dd
Timestamp: 1762374408 Timestamp [UCT]: 2025-11-05 20:26:48 Age [y:d:h:m:s]: 00:048:03:50:33
Block: 1405729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34486 RingCT/type: yes/0
Extra: 01bee99f4119e788e8b76de250d9af930a7dd88e824f693d477947fa82f1d052dd021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4842b0ab509797ebcece3aa1e3df138ec370c0cc769dc7410d84e357060aeed7 0.600000000000 1894110 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": 1405739, "vin": [ { "gen": { "height": 1405729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4842b0ab509797ebcece3aa1e3df138ec370c0cc769dc7410d84e357060aeed7" } } ], "extra": [ 1, 190, 233, 159, 65, 25, 231, 136, 232, 183, 109, 226, 80, 217, 175, 147, 10, 125, 216, 142, 130, 79, 105, 61, 71, 121, 71, 250, 130, 241, 208, 82, 221, 2, 17, 0, 0, 0, 4, 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