Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f99b02bfb93ad8f654a52177baf5f91ad1fb38494a42b89d1bdcc9ac55b2c121

Tx prefix hash: 9ca6b0e0658d382898c14f45473d986448891a9173c872d2bf5a4f776b260466
Tx public key: 4bf24ffac5971f3d43a11c3cd3c14cf0ad1b57a26f4ae3b6fcd35f02d2f9ce1c
Timestamp: 1638394274 Timestamp [UCT]: 2021-12-01 21:31:14 Age [y:d:h:m:s]: 03:067:04:29:55
Block: 386358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 826686 RingCT/type: yes/0
Extra: 014bf24ffac5971f3d43a11c3cd3c14cf0ad1b57a26f4ae3b6fcd35f02d2f9ce1c02110000001ff6cc1430000000000000000000

1 output(s) for total of 32.199081683000 dcy

stealth address amount amount idx
00: c3276e850e1e500b0c10bcb19f9855d23a69f35e0af76ac874c516ef4ee51911 32.199081683000 779489 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": 386368, "vin": [ { "gen": { "height": 386358 } } ], "vout": [ { "amount": 32199081683, "target": { "key": "c3276e850e1e500b0c10bcb19f9855d23a69f35e0af76ac874c516ef4ee51911" } } ], "extra": [ 1, 75, 242, 79, 250, 197, 151, 31, 61, 67, 161, 28, 60, 211, 193, 76, 240, 173, 27, 87, 162, 111, 74, 227, 182, 252, 211, 95, 2, 210, 249, 206, 28, 2, 17, 0, 0, 0, 31, 246, 204, 20, 48, 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