Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c6d75c4168815be97795a077eefd03dedf624a99396d1960d35f83e4c56112f

Tx prefix hash: 98091a5d76d11c6a1b407b45aa357f80371b139cba31d8cde5ee2c63a0d12373
Tx public key: 0ad7035dc3d76f07fba27bef1054b691d0b4b855bdb5ffa3b50a36e7a40d2d6d
Timestamp: 1685096517 Timestamp [UCT]: 2023-05-26 10:21:57 Age [y:d:h:m:s]: 02:167:00:27:58
Block: 768436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 639158 RingCT/type: yes/0
Extra: 010ad7035dc3d76f07fba27bef1054b691d0b4b855bdb5ffa3b50a36e7a40d2d6d021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.745230182000 dcy

stealth address amount amount idx
00: 25a5bbec8a0ae92453d198047f53d9d60a3250b6cdfc6e301b088c7e604e8218 1.745230182000 1217633 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": 768446, "vin": [ { "gen": { "height": 768436 } } ], "vout": [ { "amount": 1745230182, "target": { "key": "25a5bbec8a0ae92453d198047f53d9d60a3250b6cdfc6e301b088c7e604e8218" } } ], "extra": [ 1, 10, 215, 3, 93, 195, 215, 111, 7, 251, 162, 123, 239, 16, 84, 182, 145, 208, 180, 184, 85, 189, 181, 255, 163, 181, 10, 54, 231, 164, 13, 45, 109, 2, 17, 0, 0, 0, 2, 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