Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91b1e6881e55dbc5f0ec8e443024709b0ad6a34035a10fcdb309f5a7dc5bfc2e

Tx prefix hash: a8f9fefec2d1ed1096949a2a7a6bc98a778bdeba083205342596743a5e834a93
Tx public key: 2d0465bd21cc0d8adb33baabdbadd5a7f3a8745b94654d2f40d0cb6347263c7e
Timestamp: 1674976086 Timestamp [UCT]: 2023-01-29 07:08:06 Age [y:d:h:m:s]: 01:352:07:55:38
Block: 685161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512794 RingCT/type: yes/0
Extra: 012d0465bd21cc0d8adb33baabdbadd5a7f3a8745b94654d2f40d0cb6347263c7e0211000000015029cbac000000000000000000

1 output(s) for total of 3.294405984000 dcy

stealth address amount amount idx
00: e7de868c55d706cf73acc7be355dea6eb85d25d4cd899a87d17a10438159e111 3.294405984000 1127450 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": 685171, "vin": [ { "gen": { "height": 685161 } } ], "vout": [ { "amount": 3294405984, "target": { "key": "e7de868c55d706cf73acc7be355dea6eb85d25d4cd899a87d17a10438159e111" } } ], "extra": [ 1, 45, 4, 101, 189, 33, 204, 13, 138, 219, 51, 186, 171, 219, 173, 213, 167, 243, 168, 116, 91, 148, 101, 77, 47, 64, 208, 203, 99, 71, 38, 60, 126, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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