Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 106aa2869bab69972d797451cd8bc078b15ec8d88733c9929a56a778d208cd32

Tx prefix hash: c57871998aa81e21fcca119235d0a5f4f74523e385cc0d55703409c94eb425c1
Tx public key: ec538c9f3cd8776a99f634343baee65a974dfc8e3c64ab8af9720abe369dcb5e
Timestamp: 1581944758 Timestamp [UCT]: 2020-02-17 13:05:58 Age [y:d:h:m:s]: 04:313:02:14:11
Block: 66608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116346 RingCT/type: yes/0
Extra: 01ec538c9f3cd8776a99f634343baee65a974dfc8e3c64ab8af9720abe369dcb5e0211000000018a2ee0d9000000000000000000

1 output(s) for total of 369.233293681000 dcy

stealth address amount amount idx
00: c9afa4180ea614c2746fa8ef1b68960539c1a5bdcffd5cbc74c3c0b299c77dc0 369.233293681000 122739 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": 66618, "vin": [ { "gen": { "height": 66608 } } ], "vout": [ { "amount": 369233293681, "target": { "key": "c9afa4180ea614c2746fa8ef1b68960539c1a5bdcffd5cbc74c3c0b299c77dc0" } } ], "extra": [ 1, 236, 83, 140, 159, 60, 216, 119, 106, 153, 246, 52, 52, 59, 174, 230, 90, 151, 77, 252, 142, 60, 100, 171, 138, 249, 114, 10, 190, 54, 157, 203, 94, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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