Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 384ff4af40d4f850e35b4728507ce4cf7514caa9b4a844e557cda3bbb400b6e7

Tx prefix hash: 2f562ce98c2755abaebc87c3e59fdb35a167eb6a960ea03832cdb69800f00bef
Tx public key: eff941736f1d14fd835cde927385fb0a7d23249f12416df080af33eefda4b890
Timestamp: 1574667998 Timestamp [UCT]: 2019-11-25 07:46:38 Age [y:d:h:m:s]: 05:046:10:49:45
Block: 17020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176046 RingCT/type: yes/0
Extra: 01eff941736f1d14fd835cde927385fb0a7d23249f12416df080af33eefda4b890021100000001f95225a5000000000000000000

1 output(s) for total of 539.022080336000 dcy

stealth address amount amount idx
00: 9158d44c3b42a23ab1885766b6f52c955abd493fee5ae6dab9b5ee8a2fac565d 539.022080336000 24308 of 0

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": 17030, "vin": [ { "gen": { "height": 17020 } } ], "vout": [ { "amount": 539022080336, "target": { "key": "9158d44c3b42a23ab1885766b6f52c955abd493fee5ae6dab9b5ee8a2fac565d" } } ], "extra": [ 1, 239, 249, 65, 115, 111, 29, 20, 253, 131, 92, 222, 146, 115, 133, 251, 10, 125, 35, 36, 159, 18, 65, 109, 240, 128, 175, 51, 238, 253, 164, 184, 144, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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