Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e5c7fc78852aa8f08a18c0819ed284d7d04445744d902ffdbe2c5a0fa38cbd8

Tx prefix hash: d97e4114dda9b63bdbe8769c0e3f7036689a65d46e17780b69ad81464914613b
Tx public key: 2f6b2a483455eb8dfe51cdde259ec7311e09dbca8abef9cf5e7f3c93a9e45fa9
Timestamp: 1765566941 Timestamp [UCT]: 2025-12-12 19:15:41 Age [y:d:h:m:s]: 00:018:21:30:33
Block: 1432197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13527 RingCT/type: yes/0
Extra: 012f6b2a483455eb8dfe51cdde259ec7311e09dbca8abef9cf5e7f3c93a9e45fa902110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5614180af8ff6d93359278f07d510946e4a0ccbf8ff54e36ac2e8e2dabcf1eef 0.600000000000 1920976 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": 1432207, "vin": [ { "gen": { "height": 1432197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5614180af8ff6d93359278f07d510946e4a0ccbf8ff54e36ac2e8e2dabcf1eef" } } ], "extra": [ 1, 47, 107, 42, 72, 52, 85, 235, 141, 254, 81, 205, 222, 37, 158, 199, 49, 30, 9, 219, 202, 138, 190, 249, 207, 94, 127, 60, 147, 169, 228, 95, 169, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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