Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 017427bf484d327b34177ab8f4868674fdc6ac987fdf1d36d880baaca9a0be60

Tx prefix hash: 1b3fa22b327ea612c1f0dd3b5bf6aafb0bbc4397d9a86aa5f09c60ef4c60dc91
Tx public key: e6996533a185463bb7e74b38fa5c0db596b2e199edbd0d3d53cc885ef402a318
Timestamp: 1708236670 Timestamp [UCT]: 2024-02-18 06:11:10 Age [y:d:h:m:s]: 01:060:04:03:09
Block: 960030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304044 RingCT/type: yes/0
Extra: 01e6996533a185463bb7e74b38fa5c0db596b2e199edbd0d3d53cc885ef402a3180211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25c332190f371e68fd842f72a84b7a1206af7a25fc89b023d858abe9d0f1428e 0.600000000000 1419589 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": 960040, "vin": [ { "gen": { "height": 960030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25c332190f371e68fd842f72a84b7a1206af7a25fc89b023d858abe9d0f1428e" } } ], "extra": [ 1, 230, 153, 101, 51, 161, 133, 70, 59, 183, 231, 75, 56, 250, 92, 13, 181, 150, 178, 225, 153, 237, 189, 13, 61, 83, 204, 136, 94, 244, 2, 163, 24, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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