Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 953b7cf91fe29ffd4b6d4b4561013ac5ec43ff6384d18b81eac0c93d265eb287

Tx prefix hash: 661d1cab3238887db41a3feedb2b7739fdbb46326deeeb72fb51e5ad2174f42f
Tx public key: 7ef5de8d97ccc94c9ac667723c83257fd25dd5501bf71f18f38920bfe23d326a
Timestamp: 1720794271 Timestamp [UCT]: 2024-07-12 14:24:31 Age [y:d:h:m:s]: 00:293:11:40:00
Block: 1064159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209685 RingCT/type: yes/0
Extra: 017ef5de8d97ccc94c9ac667723c83257fd25dd5501bf71f18f38920bfe23d326a02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e311d7b79a260a7e319ca1fdb5d86f859fc59939a974a1adf4ae9821d12b5227 0.600000000000 1534682 of 15

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": 1064169, "vin": [ { "gen": { "height": 1064159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e311d7b79a260a7e319ca1fdb5d86f859fc59939a974a1adf4ae9821d12b5227" } } ], "extra": [ 1, 126, 245, 222, 141, 151, 204, 201, 76, 154, 198, 103, 114, 60, 131, 37, 127, 210, 93, 213, 80, 27, 247, 31, 24, 243, 137, 32, 191, 226, 61, 50, 106, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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