Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9699a3ed440f1fef59ce648669b526da01d6e93fb5764fd3915a63265e8760ea

Tx prefix hash: d039666d79db0cf200bb56fe3e57c19aadf1337c6e7a7178508bb3d8e9751cc2
Tx public key: f7aa33923970f411396d83d67e47ce7cc6a5bd3ff2ecb8a45ef3a58dbbbba30e
Timestamp: 1730856757 Timestamp [UCT]: 2024-11-06 01:32:37 Age [y:d:h:m:s]: 00:053:16:03:44
Block: 1147469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38405 RingCT/type: yes/0
Extra: 01f7aa33923970f411396d83d67e47ce7cc6a5bd3ff2ecb8a45ef3a58dbbbba30e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e3415487350732ae651f0a339e8bea95c9e33c17909eee5da42df1fad1f4eaa 0.600000000000 1632166 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": 1147479, "vin": [ { "gen": { "height": 1147469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e3415487350732ae651f0a339e8bea95c9e33c17909eee5da42df1fad1f4eaa" } } ], "extra": [ 1, 247, 170, 51, 146, 57, 112, 244, 17, 57, 109, 131, 214, 126, 71, 206, 124, 198, 165, 189, 63, 242, 236, 184, 164, 94, 243, 165, 141, 187, 187, 163, 14, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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