Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dad77bf398cf14c582359dd4d0f5d2f19a205cc4c55150de192fb48ac5164193

Tx prefix hash: 1e5d36fafebf968b8f561a3414bbceba62f60013902d32a0e7a3a6c2c1a9bd59
Tx public key: 1df06d3b465448798d21de2d33ea9c8bf80915e73d5f87908b92fa628b7f9aa8
Timestamp: 1763634790 Timestamp [UCT]: 2025-11-20 10:33:10 Age [y:d:h:m:s]: 00:007:08:10:29
Block: 1416170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5278 RingCT/type: yes/0
Extra: 011df06d3b465448798d21de2d33ea9c8bf80915e73d5f87908b92fa628b7f9aa80211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e880cf25362ff3fff02d8f2a18ef4e2b3658ecbe6d50165195329b31e04d2289 0.600000000000 1904689 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": 1416180, "vin": [ { "gen": { "height": 1416170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e880cf25362ff3fff02d8f2a18ef4e2b3658ecbe6d50165195329b31e04d2289" } } ], "extra": [ 1, 29, 240, 109, 59, 70, 84, 72, 121, 141, 33, 222, 45, 51, 234, 156, 139, 248, 9, 21, 231, 61, 95, 135, 144, 139, 146, 250, 98, 139, 127, 154, 168, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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