Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a97f19f337246f4bb42154cdcc8c9d85eba4ac5f5e0bf13e6b8da97470343345

Tx prefix hash: ffc9877ee99fb6330a74f05ad6f87d4688462fbe99a19ed96916893883242daa
Tx public key: 78f2e371ce33a31c62c44137eaff7c402b87fda2aa4cc937e37e64f091e312c0
Timestamp: 1708789371 Timestamp [UCT]: 2024-02-24 15:42:51 Age [y:d:h:m:s]: 00:321:03:09:14
Block: 964624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229875 RingCT/type: yes/0
Extra: 0178f2e371ce33a31c62c44137eaff7c402b87fda2aa4cc937e37e64f091e312c002110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 102403e680ff2829b99a4fd172cfcb78ac4e9d65817ff9354089ec1c50e6c16b 0.600000000000 1424365 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": 964634, "vin": [ { "gen": { "height": 964624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "102403e680ff2829b99a4fd172cfcb78ac4e9d65817ff9354089ec1c50e6c16b" } } ], "extra": [ 1, 120, 242, 227, 113, 206, 51, 163, 28, 98, 196, 65, 55, 234, 255, 124, 64, 43, 135, 253, 162, 170, 76, 201, 55, 227, 126, 100, 240, 145, 227, 18, 192, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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