Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24c912d86c81e9594324d2c50c61d1c62dcbeb7fa612f63a8df4e6c5fe414841

Tx prefix hash: b6366256e2adebb52a7f1323978edb89bad0efaae0df92c2de198ff720ee6a15
Tx public key: d3238c86ff76d11b13eb86da6cb8a8726ba9d251344c5b952fbac67030880882
Timestamp: 1705237415 Timestamp [UCT]: 2024-01-14 13:03:35 Age [y:d:h:m:s]: 01:110:08:27:59
Block: 935155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339985 RingCT/type: yes/0
Extra: 01d3238c86ff76d11b13eb86da6cb8a8726ba9d251344c5b952fbac6703088088202110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f8377333f367e8bd9f986335bff35249ea0170d0336eb06d3538e0d3a9b79ea 0.600000000000 1393171 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": 935165, "vin": [ { "gen": { "height": 935155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f8377333f367e8bd9f986335bff35249ea0170d0336eb06d3538e0d3a9b79ea" } } ], "extra": [ 1, 211, 35, 140, 134, 255, 118, 209, 27, 19, 235, 134, 218, 108, 184, 168, 114, 107, 169, 210, 81, 52, 76, 91, 149, 47, 186, 198, 112, 48, 136, 8, 130, 2, 17, 0, 0, 0, 2, 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