Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f19fe2376afadbf0fb4d16a3a448917d21e855b55aa63dde91c8465fd740be41

Tx prefix hash: 808afa0bbe1ef447ed014f3cd3a57d389bbdbab56538cd0a253c387e31a4bd53
Tx public key: 8187eac60b3cd259393d6b25b5f2eff13e6e9d912ce38a829f0b56e43bf4aceb
Timestamp: 1765911934 Timestamp [UCT]: 2025-12-16 19:05:34 Age [y:d:h:m:s]: 00:013:08:33:20
Block: 1435043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9571 RingCT/type: yes/0
Extra: 018187eac60b3cd259393d6b25b5f2eff13e6e9d912ce38a829f0b56e43bf4aceb021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ebf4a6bec5a4521670c345a6d67df164c6c479fac5f84a2bd3dcdf1382401f2 0.600000000000 1923840 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": 1435053, "vin": [ { "gen": { "height": 1435043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ebf4a6bec5a4521670c345a6d67df164c6c479fac5f84a2bd3dcdf1382401f2" } } ], "extra": [ 1, 129, 135, 234, 198, 11, 60, 210, 89, 57, 61, 107, 37, 181, 242, 239, 241, 62, 110, 157, 145, 44, 227, 138, 130, 159, 11, 86, 228, 59, 244, 172, 235, 2, 17, 0, 0, 0, 9, 214, 225, 157, 124, 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