Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a049cf90e72e66c5bdee4cbd9f4ec2e6b675e8b826e66cfda618a9c3f68906b3

Tx prefix hash: e225d6bd8a1a16f02649e8c54ff750b65e6cc1a938859a595d14e817da50bc1e
Tx public key: 75909b3af95cf7e6cfcde3137d99ac474d0ede870c601e96e3f8142979fc5d09
Timestamp: 1718263141 Timestamp [UCT]: 2024-06-13 07:19:01 Age [y:d:h:m:s]: 00:274:17:31:30
Block: 1043157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196334 RingCT/type: yes/0
Extra: 0175909b3af95cf7e6cfcde3137d99ac474d0ede870c601e96e3f8142979fc5d090211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 120c6b582e6ade70df061d945125e720e7e8c385161468f5eb207d1323ac3118 0.600000000000 1512242 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": 1043167, "vin": [ { "gen": { "height": 1043157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "120c6b582e6ade70df061d945125e720e7e8c385161468f5eb207d1323ac3118" } } ], "extra": [ 1, 117, 144, 155, 58, 249, 92, 247, 230, 207, 205, 227, 19, 125, 153, 172, 71, 77, 14, 222, 135, 12, 96, 30, 150, 227, 248, 20, 41, 121, 252, 93, 9, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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