Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2521434d9f8f58205e89b91868e61342273c05895c0a4f1e4b3613386922074

Tx prefix hash: ef7db12477ac7d112c76a2192c7c74f8969ad89ca04200fbdfc3fcc0af39b551
Tx public key: 2cc4a32ed1aaeab1ed74b9b1a5ee7516c8deeddd4bc1e89712c48f164a2499d7
Timestamp: 1743088121 Timestamp [UCT]: 2025-03-27 15:08:41 Age [y:d:h:m:s]: 00:245:18:22:50
Block: 1248473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173410 RingCT/type: yes/0
Extra: 012cc4a32ed1aaeab1ed74b9b1a5ee7516c8deeddd4bc1e89712c48f164a2499d7021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b981e4e06b2f9134730a95ca0b3d156b734367b0ebad39c464db4fdaf6cbe22d 0.600000000000 1735502 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": 1248483, "vin": [ { "gen": { "height": 1248473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b981e4e06b2f9134730a95ca0b3d156b734367b0ebad39c464db4fdaf6cbe22d" } } ], "extra": [ 1, 44, 196, 163, 46, 209, 170, 234, 177, 237, 116, 185, 177, 165, 238, 117, 22, 200, 222, 237, 221, 75, 193, 232, 151, 18, 196, 143, 22, 74, 36, 153, 215, 2, 17, 0, 0, 0, 1, 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