Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36fd25043e25033e858de25718c07669be88e14839e1e626bd7e7f981302b92f

Tx prefix hash: e510c7a251d9ce1b7214c6e4392982e8e68a9b5ae7190a21bad437de6feeb17e
Tx public key: 8059f147dbd8b2cda4d1fb0e643810255d9a04bf6c49c3d2c1268454cc4fcbb1
Timestamp: 1716156887 Timestamp [UCT]: 2024-05-19 22:14:47 Age [y:d:h:m:s]: 00:235:22:03:47
Block: 1025690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168855 RingCT/type: yes/0
Extra: 018059f147dbd8b2cda4d1fb0e643810255d9a04bf6c49c3d2c1268454cc4fcbb102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 191d3f73a7e99db70bced8793c04e8292abc2159b589b1229fac48d68f2f7cfb 0.600000000000 1492369 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": 1025700, "vin": [ { "gen": { "height": 1025690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "191d3f73a7e99db70bced8793c04e8292abc2159b589b1229fac48d68f2f7cfb" } } ], "extra": [ 1, 128, 89, 241, 71, 219, 216, 178, 205, 164, 209, 251, 14, 100, 56, 16, 37, 93, 154, 4, 191, 108, 73, 195, 210, 193, 38, 132, 84, 204, 79, 203, 177, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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