Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b95869bdf78646789096beb616ebbf4781f461f7c21a612ea1c63ea77c4f5d0c

Tx prefix hash: 69b760b9f18229f74929d1e14ad33c8525a1dbf9544fa619781fcf126108c46a
Tx public key: fd0f8e3de95c40ff0d64a440e8de4002a55f542a253da5f7f4bb4ac3f2384e84
Timestamp: 1727950233 Timestamp [UCT]: 2024-10-03 10:10:33 Age [y:d:h:m:s]: 00:183:17:51:57
Block: 1123471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131113 RingCT/type: yes/0
Extra: 01fd0f8e3de95c40ff0d64a440e8de4002a55f542a253da5f7f4bb4ac3f2384e84021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f63945150b433dbe724940434016a35e4edd30f940710698d5c6d31d0af8830 0.600000000000 1606006 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": 1123481, "vin": [ { "gen": { "height": 1123471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f63945150b433dbe724940434016a35e4edd30f940710698d5c6d31d0af8830" } } ], "extra": [ 1, 253, 15, 142, 61, 233, 92, 64, 255, 13, 100, 164, 64, 232, 222, 64, 2, 165, 95, 84, 42, 37, 61, 165, 247, 244, 187, 74, 195, 242, 56, 78, 132, 2, 17, 0, 0, 0, 3, 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