Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca338c3b4cd1e6077c85add0af1b1cc233e8b95dfcf25093f6fa62a7044c74b8

Tx prefix hash: 417049ef2c503ef66835a3af69e8ec18baa53d4338f9bef219229de678ce1255
Tx public key: e8665b8affd9c670dbef03b44e53f0f6aad29cedd8934bfd07072d0cc4b17ecc
Timestamp: 1697405157 Timestamp [UCT]: 2023-10-15 21:25:57 Age [y:d:h:m:s]: 01:174:03:29:32
Block: 870437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385479 RingCT/type: yes/0
Extra: 01e8665b8affd9c670dbef03b44e53f0f6aad29cedd8934bfd07072d0cc4b17ecc021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.801458262000 dcy

stealth address amount amount idx
00: 3de1c135b22a31e55a907d219fe6c0e597d0358820145a9d91991f2f08605cf5 0.801458262000 1325316 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": 870447, "vin": [ { "gen": { "height": 870437 } } ], "vout": [ { "amount": 801458262, "target": { "key": "3de1c135b22a31e55a907d219fe6c0e597d0358820145a9d91991f2f08605cf5" } } ], "extra": [ 1, 232, 102, 91, 138, 255, 217, 198, 112, 219, 239, 3, 180, 78, 83, 240, 246, 170, 210, 156, 237, 216, 147, 75, 253, 7, 7, 45, 12, 196, 177, 126, 204, 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