Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86a390b1c9bfc66e0b6e4e1fe7850937fb7d09377902653c83cef7e08cc88935

Tx prefix hash: b42ece27ebdfb300e1ebcd7898287528c00b75ca6e1e1d5a846c4c137d44728e
Tx public key: 70a3b6d91d5f1af7f85adeed44df0a6c743204cf9f5a7de8fbf2ebf72ed882d1
Timestamp: 1705936385 Timestamp [UCT]: 2024-01-22 15:13:05 Age [y:d:h:m:s]: 00:354:11:43:17
Block: 940924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253813 RingCT/type: yes/0
Extra: 0170a3b6d91d5f1af7f85adeed44df0a6c743204cf9f5a7de8fbf2ebf72ed882d102110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f881a4c06dc920a2a205cc24d918b8fd45f31ec10a7c4f414716aa8805f49830 0.600000000000 1399064 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": 940934, "vin": [ { "gen": { "height": 940924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f881a4c06dc920a2a205cc24d918b8fd45f31ec10a7c4f414716aa8805f49830" } } ], "extra": [ 1, 112, 163, 182, 217, 29, 95, 26, 247, 248, 90, 222, 237, 68, 223, 10, 108, 116, 50, 4, 207, 159, 90, 125, 232, 251, 242, 235, 247, 46, 216, 130, 209, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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