Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 686ae6b1ea1c556aee2002643af412298d9bbb55181d3bcf94e3700f8711c0ac

Tx prefix hash: e86d630c04c8047cc70eceebb99dbe5b77fefb62e529badc6e1cbe3dc4a492b0
Tx public key: e77bd88fdf7838e1a4f7ed4e435b77d8fdaf7fc7da7f9df5f91d4415a790ca6e
Timestamp: 1575977926 Timestamp [UCT]: 2019-12-10 11:38:46 Age [y:d:h:m:s]: 05:188:23:44:20
Block: 24864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1280637 RingCT/type: yes/0
Extra: 01e77bd88fdf7838e1a4f7ed4e435b77d8fdaf7fc7da7f9df5f91d4415a790ca6e02110000000d9159db1e000000000000000000

1 output(s) for total of 507.710466211000 dcy

stealth address amount amount idx
00: 4e7cc18af91ab21fb2f412e0afab11cedc9ba80d206c0b33b7bbf010c6499034 507.710466211000 40829 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": 24874, "vin": [ { "gen": { "height": 24864 } } ], "vout": [ { "amount": 507710466211, "target": { "key": "4e7cc18af91ab21fb2f412e0afab11cedc9ba80d206c0b33b7bbf010c6499034" } } ], "extra": [ 1, 231, 123, 216, 143, 223, 120, 56, 225, 164, 247, 237, 78, 67, 91, 119, 216, 253, 175, 127, 199, 218, 127, 157, 245, 249, 29, 68, 21, 167, 144, 202, 110, 2, 17, 0, 0, 0, 13, 145, 89, 219, 30, 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