Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a16b0a5c83f2c8dacd1e3a5b1cdadc8ca9ee315e51ac73acc38eb16f1e3ee86

Tx prefix hash: ed2c5780c8d6212489e2ec04c5bd055b0e6ddafb598fb47e2f580bdaee1bc7dd
Tx public key: 25024a9badb6a7cc919770c457f2bce3ceddcd69c13af7677be5df9c690f90fb
Timestamp: 1574553972 Timestamp [UCT]: 2019-11-24 00:06:12 Age [y:d:h:m:s]: 04:349:07:29:33
Block: 16017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1131637 RingCT/type: yes/0
Extra: 0125024a9badb6a7cc919770c457f2bce3ceddcd69c13af7677be5df9c690f90fb021100000008f95225a5000000000000000000

1 output(s) for total of 543.172037747000 dcy

stealth address amount amount idx
00: 183cd242721cff827dc5fc79c4facef7f9f1bba3b50d3030233b52a62ca9d9d3 543.172037747000 22038 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": 16027, "vin": [ { "gen": { "height": 16017 } } ], "vout": [ { "amount": 543172037747, "target": { "key": "183cd242721cff827dc5fc79c4facef7f9f1bba3b50d3030233b52a62ca9d9d3" } } ], "extra": [ 1, 37, 2, 74, 155, 173, 182, 167, 204, 145, 151, 112, 196, 87, 242, 188, 227, 206, 221, 205, 105, 193, 58, 247, 103, 123, 229, 223, 156, 105, 15, 144, 251, 2, 17, 0, 0, 0, 8, 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