Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 739b0557b9dd9e525d89946e8802207e3c55beed05754b4083c5292882f6e5d5

Tx prefix hash: 7fdda6f558eed27c93c902c2c9bc4df918c63aeaf5d617b7af322da906386ee4
Tx public key: fd4b41d8e7f25599e9d3fbcaa0f8b196865ff90e557018627a2c01d36c5e9b23
Timestamp: 1700413622 Timestamp [UCT]: 2023-11-19 17:07:02 Age [y:d:h:m:s]: 01:179:03:14:03
Block: 895175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389228 RingCT/type: yes/0
Extra: 01fd4b41d8e7f25599e9d3fbcaa0f8b196865ff90e557018627a2c01d36c5e9b23021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.663611052000 dcy

stealth address amount amount idx
00: 17fc7314a7be370cc5383cdf3e3585433cc6dd13058951ccd6225948b3387ea5 0.663611052000 1351398 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": 895185, "vin": [ { "gen": { "height": 895175 } } ], "vout": [ { "amount": 663611052, "target": { "key": "17fc7314a7be370cc5383cdf3e3585433cc6dd13058951ccd6225948b3387ea5" } } ], "extra": [ 1, 253, 75, 65, 216, 231, 242, 85, 153, 233, 211, 251, 202, 160, 248, 177, 150, 134, 95, 249, 14, 85, 112, 24, 98, 122, 44, 1, 211, 108, 94, 155, 35, 2, 17, 0, 0, 0, 6, 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