Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00287f5b4d7cfe9b490b7b3d8af55ed88a49ce3b4cc77b73b991e3813a0893c0

Tx prefix hash: 60039bafa42c8ff72a943f9165e092ee7042a9becd66c0f80dbb1239dbebd098
Tx public key: 058e3cb9f2461299f49575ef350d5afd971bbf7312708c07ee4b9ed9a988eba9
Timestamp: 1684140115 Timestamp [UCT]: 2023-05-15 08:41:55 Age [y:d:h:m:s]: 02:175:17:08:58
Block: 760498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645383 RingCT/type: yes/0
Extra: 01058e3cb9f2461299f49575ef350d5afd971bbf7312708c07ee4b9ed9a988eba9021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.854191629000 dcy

stealth address amount amount idx
00: c50f4dbb24e7f39c5d79e49589fc1f2d8ab602a7af4cd9cf8710ef59398d3b2f 1.854191629000 1209107 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": 760508, "vin": [ { "gen": { "height": 760498 } } ], "vout": [ { "amount": 1854191629, "target": { "key": "c50f4dbb24e7f39c5d79e49589fc1f2d8ab602a7af4cd9cf8710ef59398d3b2f" } } ], "extra": [ 1, 5, 142, 60, 185, 242, 70, 18, 153, 244, 149, 117, 239, 53, 13, 90, 253, 151, 27, 191, 115, 18, 112, 140, 7, 238, 75, 158, 217, 169, 136, 235, 169, 2, 17, 0, 0, 0, 4, 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