Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c06a3aa0ef939408b6c5a90b646a875dc1f98333322be3dcaf0d00cd94d00df

Tx prefix hash: ccba366da0a4c0efa8be1ce4d3cff7699b05a1e68460b9a7dc4a08d3c1d66baf
Tx public key: 64c8233f1b2681d66c2e22e84b176aa1e56acc0784164b24ec47a0ef7eeff197
Timestamp: 1696812578 Timestamp [UCT]: 2023-10-09 00:49:38 Age [y:d:h:m:s]: 01:179:17:38:01
Block: 865536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389480 RingCT/type: yes/0
Extra: 0164c8233f1b2681d66c2e22e84b176aa1e56acc0784164b24ec47a0ef7eeff19702110000000741ee1c9b000000000000000000

1 output(s) for total of 0.831993560000 dcy

stealth address amount amount idx
00: 66a2a8550e8118737e22947978ffaff3d984db2e0bcdd14ba2e9fa7f2bb4d3fb 0.831993560000 1320072 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": 865546, "vin": [ { "gen": { "height": 865536 } } ], "vout": [ { "amount": 831993560, "target": { "key": "66a2a8550e8118737e22947978ffaff3d984db2e0bcdd14ba2e9fa7f2bb4d3fb" } } ], "extra": [ 1, 100, 200, 35, 63, 27, 38, 129, 214, 108, 46, 34, 232, 75, 23, 106, 161, 229, 106, 204, 7, 132, 22, 75, 36, 236, 71, 160, 239, 126, 239, 241, 151, 2, 17, 0, 0, 0, 7, 65, 238, 28, 155, 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