Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8242760edf9011c877e7b43b0a822985b4dd3da4463c5803f5eb24035835671

Tx prefix hash: ac5fda9c86457ca933f5b2740433c36b4c0dbd67f326653296545ed17cd28b8c
Tx public key: 4b59ecd76e99006815028797b11c99b402ce51f70ccdf8ac1fc9c9aa6ac99463
Timestamp: 1648584121 Timestamp [UCT]: 2022-03-29 20:02:01 Age [y:d:h:m:s]: 02:350:23:08:32
Block: 469094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 770230 RingCT/type: yes/0
Extra: 014b59ecd76e99006815028797b11c99b402ce51f70ccdf8ac1fc9c9aa6ac99463021100000008a272b9cb000000000000000000

1 output(s) for total of 17.127623141000 dcy

stealth address amount amount idx
00: 6ddd2cc9264af6769fb70ba1a9e6f22281a0101cb472f1d681684eda3ee6d9db 17.127623141000 887960 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": 469104, "vin": [ { "gen": { "height": 469094 } } ], "vout": [ { "amount": 17127623141, "target": { "key": "6ddd2cc9264af6769fb70ba1a9e6f22281a0101cb472f1d681684eda3ee6d9db" } } ], "extra": [ 1, 75, 89, 236, 215, 110, 153, 0, 104, 21, 2, 135, 151, 177, 28, 153, 180, 2, 206, 81, 247, 12, 205, 248, 172, 31, 201, 201, 170, 106, 201, 148, 99, 2, 17, 0, 0, 0, 8, 162, 114, 185, 203, 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