Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25ea47f66fcfa3e005df1f48ea5268d068c5de4d9f99614eddcd3d174931ea1c

Tx prefix hash: 67fb346a2078058d0d3b878f67dc276104e2f476a762e270b0e3a1d7675d2ed2
Tx public key: 1e0ff69d0bcefb7d958134ac081cf7dc9af9fe00c04a5198c58ee7233493af07
Timestamp: 1738084305 Timestamp [UCT]: 2025-01-28 17:11:45 Age [y:d:h:m:s]: 00:138:20:28:27
Block: 1207078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99190 RingCT/type: yes/0
Extra: 011e0ff69d0bcefb7d958134ac081cf7dc9af9fe00c04a5198c58ee7233493af07021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcd4f692ce1108d7855502a4bd841fe6d7010afc7b1631c12d7b71428201e10d 0.600000000000 1693799 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": 1207088, "vin": [ { "gen": { "height": 1207078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcd4f692ce1108d7855502a4bd841fe6d7010afc7b1631c12d7b71428201e10d" } } ], "extra": [ 1, 30, 15, 246, 157, 11, 206, 251, 125, 149, 129, 52, 172, 8, 28, 247, 220, 154, 249, 254, 0, 192, 74, 81, 152, 197, 142, 231, 35, 52, 147, 175, 7, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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