Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65b5fae8e0f5b3e5c0b9f22fd8d67ce77eb5a6c285d6dd904cd91fbac4296326

Tx prefix hash: 90c2475b422b26b61ce7fe96afe6cbd3e573fec7c8cceecc5f42423c6911037a
Tx public key: 66c8777a6a7ca53dfcd09d9642b95f9acd046a5747a728782f6e9ec8ee65fdcf
Timestamp: 1658116052 Timestamp [UCT]: 2022-07-18 03:47:32 Age [y:d:h:m:s]: 02:212:10:35:23
Block: 546176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 672969 RingCT/type: yes/0
Extra: 0166c8777a6a7ca53dfcd09d9642b95f9acd046a5747a728782f6e9ec8ee65fdcf02110000001cd3fcec30000000000000000000

1 output(s) for total of 9.512448563000 dcy

stealth address amount amount idx
00: 73e3692fb6a830f91dbc0cf12cdca667ac8d78d7dfe18524a08249b844455947 9.512448563000 977163 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": 546186, "vin": [ { "gen": { "height": 546176 } } ], "vout": [ { "amount": 9512448563, "target": { "key": "73e3692fb6a830f91dbc0cf12cdca667ac8d78d7dfe18524a08249b844455947" } } ], "extra": [ 1, 102, 200, 119, 122, 106, 124, 165, 61, 252, 208, 157, 150, 66, 185, 95, 154, 205, 4, 106, 87, 71, 167, 40, 120, 47, 110, 158, 200, 238, 101, 253, 207, 2, 17, 0, 0, 0, 28, 211, 252, 236, 48, 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