Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 669f8f820722536447a0bb9aed7e164753adcab28c45dd5b45c9bd30189e0cdf

Tx prefix hash: 06ba8622ae2397284fa53ab54caa40c94fa86efbc702051dc00a33256a967d08
Tx public key: e317f8ae88a92f5f0220afef3a98a5c737e8787fc49b780eeba3e9602a846f28
Timestamp: 1685614945 Timestamp [UCT]: 2023-06-01 10:22:25 Age [y:d:h:m:s]: 01:271:23:10:04
Block: 772742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455534 RingCT/type: yes/0
Extra: 01e317f8ae88a92f5f0220afef3a98a5c737e8787fc49b780eeba3e9602a846f2802110000000575e3f0e9000000000000000000

1 output(s) for total of 1.688826921000 dcy

stealth address amount amount idx
00: 961908b7e96636adcc444e4fb23c3b02c35ce632e0b3551ec0351266ca8b17ec 1.688826921000 1222171 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": 772752, "vin": [ { "gen": { "height": 772742 } } ], "vout": [ { "amount": 1688826921, "target": { "key": "961908b7e96636adcc444e4fb23c3b02c35ce632e0b3551ec0351266ca8b17ec" } } ], "extra": [ 1, 227, 23, 248, 174, 136, 169, 47, 95, 2, 32, 175, 239, 58, 152, 165, 199, 55, 232, 120, 127, 196, 155, 120, 14, 235, 163, 233, 96, 42, 132, 111, 40, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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