Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc8f5ff8455acc2f256d88afd3fa5fcbfc1e6b7903f7f21d8267b722514fe6d0

Tx prefix hash: ead2f4faa50f98d74faed666110cd39ccc7c0e9ff508b289d5867146720160aa
Tx public key: 7cef22ded81add1c5a5cb6950e699dccdb14c07d1ef33596811c9789d6fbea92
Timestamp: 1717768173 Timestamp [UCT]: 2024-06-07 13:49:33 Age [y:d:h:m:s]: 00:282:13:06:50
Block: 1039065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201909 RingCT/type: yes/0
Extra: 017cef22ded81add1c5a5cb6950e699dccdb14c07d1ef33596811c9789d6fbea9202110000001459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7e500e7f1461b5b4cc903f188f8003ba0d212acffedd0ecd14363389a5e542d 0.600000000000 1507652 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": 1039075, "vin": [ { "gen": { "height": 1039065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7e500e7f1461b5b4cc903f188f8003ba0d212acffedd0ecd14363389a5e542d" } } ], "extra": [ 1, 124, 239, 34, 222, 216, 26, 221, 28, 90, 92, 182, 149, 14, 105, 157, 204, 219, 20, 192, 125, 30, 243, 53, 150, 129, 28, 151, 137, 214, 251, 234, 146, 2, 17, 0, 0, 0, 20, 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