Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b0ac4b92c4ccef8b01285feca86bd6e170898e57693bb8bb5aaf9f64cde7455

Tx prefix hash: fd8286041c2161eea35992f255f503666b869a3bb188cf23711fbf4731c3ac21
Tx public key: 0a3acbcf6b240394556f7fb7014c610d357a98e22c08c0361cc18b443f87d3ae
Timestamp: 1581824397 Timestamp [UCT]: 2020-02-16 03:39:57 Age [y:d:h:m:s]: 04:284:17:46:39
Block: 66032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1095633 RingCT/type: yes/0
Extra: 010a3acbcf6b240394556f7fb7014c610d357a98e22c08c0361cc18b443f87d3ae021100000006c71d3ff9000000000000000000

1 output(s) for total of 370.859477673000 dcy

stealth address amount amount idx
00: 1f4a241a49d31081c07c588c28db8eab6691ef0b5d5df0aa6d79b20f77082393 370.859477673000 121675 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": 66042, "vin": [ { "gen": { "height": 66032 } } ], "vout": [ { "amount": 370859477673, "target": { "key": "1f4a241a49d31081c07c588c28db8eab6691ef0b5d5df0aa6d79b20f77082393" } } ], "extra": [ 1, 10, 58, 203, 207, 107, 36, 3, 148, 85, 111, 127, 183, 1, 76, 97, 13, 53, 122, 152, 226, 44, 8, 192, 54, 28, 193, 139, 68, 63, 135, 211, 174, 2, 17, 0, 0, 0, 6, 199, 29, 63, 249, 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