Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73ad97dd67eb743aa6baf00d60965ff54fa35a2badd3c28ff8b2df10c51e871d

Tx prefix hash: 008d77be0f8420aaf40b155c27449df05e8845722d17ad4284d406d92bc0a12e
Tx public key: a838fd9c8c8b2b66ee533255c1221e72077440521ed540e3ff11b710248ff165
Timestamp: 1578717548 Timestamp [UCT]: 2020-01-11 04:39:08 Age [y:d:h:m:s]: 04:314:20:15:48
Block: 43069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114414 RingCT/type: yes/0
Extra: 01a838fd9c8c8b2b66ee533255c1221e72077440521ed540e3ff11b710248ff165021100000017d81c26c0000000000000000000

1 output(s) for total of 441.870865290000 dcy

stealth address amount amount idx
00: d09e2471f7d1429392573746961a31e4ff2d1fb0a881a6d4917cee086dfa9d23 441.870865290000 77825 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": 43079, "vin": [ { "gen": { "height": 43069 } } ], "vout": [ { "amount": 441870865290, "target": { "key": "d09e2471f7d1429392573746961a31e4ff2d1fb0a881a6d4917cee086dfa9d23" } } ], "extra": [ 1, 168, 56, 253, 156, 140, 139, 43, 102, 238, 83, 50, 85, 193, 34, 30, 114, 7, 116, 64, 82, 30, 213, 64, 227, 255, 17, 183, 16, 36, 143, 241, 101, 2, 17, 0, 0, 0, 23, 216, 28, 38, 192, 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