Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a882905d982f02bf57ea04e11d3098b73c7cf6764e57e1ac9824ac514f8e949

Tx prefix hash: f4d4bb8ddaa779d5c27100a8c28f7dbb3169d95705ea754ee2879abc90c76ec1
Tx public key: ad845e8b677f466c2f3c48899b69f9ac6807d30f2649142ae3ba27a7e2fcd4fe
Timestamp: 1724897953 Timestamp [UCT]: 2024-08-29 02:19:13 Age [y:d:h:m:s]: 00:241:06:23:45
Block: 1098160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172303 RingCT/type: yes/0
Extra: 01ad845e8b677f466c2f3c48899b69f9ac6807d30f2649142ae3ba27a7e2fcd4fe021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00f568ada547cb09399fc21d633e8d7cc1a8a118231cebff6e0e7de87e57d91d 0.600000000000 1573779 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": 1098170, "vin": [ { "gen": { "height": 1098160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00f568ada547cb09399fc21d633e8d7cc1a8a118231cebff6e0e7de87e57d91d" } } ], "extra": [ 1, 173, 132, 94, 139, 103, 127, 70, 108, 47, 60, 72, 137, 155, 105, 249, 172, 104, 7, 211, 15, 38, 73, 20, 42, 227, 186, 39, 167, 226, 252, 212, 254, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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