Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d358765364fcd93947bbe86b1d5eaed2d9db34bf8f2372376e4ee6db753ef59

Tx prefix hash: c9111c67ef13a10e7b2b8a791af0ec9cf37337045d27f907474b37c319afeab1
Tx public key: 38ee75d060490ecf6f5e7051c27b50000e97330a79efdd95b1c40df9ec9a5d77
Timestamp: 1696095901 Timestamp [UCT]: 2023-09-30 17:45:01 Age [y:d:h:m:s]: 01:240:04:13:13
Block: 859578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432747 RingCT/type: yes/0
Extra: 0138ee75d060490ecf6f5e7051c27b50000e97330a79efdd95b1c40df9ec9a5d77021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.870685478000 dcy

stealth address amount amount idx
00: fff8b4eed19d0f991f12d047a11fa73fe52f8342b82a8b6d25e6642eccaec894 0.870685478000 1313810 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": 859588, "vin": [ { "gen": { "height": 859578 } } ], "vout": [ { "amount": 870685478, "target": { "key": "fff8b4eed19d0f991f12d047a11fa73fe52f8342b82a8b6d25e6642eccaec894" } } ], "extra": [ 1, 56, 238, 117, 208, 96, 73, 14, 207, 111, 94, 112, 81, 194, 123, 80, 0, 14, 151, 51, 10, 121, 239, 221, 149, 177, 196, 13, 249, 236, 154, 93, 119, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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