Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e2f665453580f771e9bc48b6197f73074606dc75e17e3501cb3e5eaddea2c90

Tx prefix hash: 00e11b34f918847719d136c617a018f1ebccb2aa1a98190049c4751673ffce89
Tx public key: e9fa802724cae4f9953c2e0f41cb22f97813a6f771b8a59c741d5dc79baab096
Timestamp: 1712823867 Timestamp [UCT]: 2024-04-11 08:24:27 Age [y:d:h:m:s]: 01:272:06:46:54
Block: 998033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453378 RingCT/type: yes/0
Extra: 01e9fa802724cae4f9953c2e0f41cb22f97813a6f771b8a59c741d5dc79baab0960211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e7b18614e90db0a5823e7479e8da8237f387d0a3a4e7934ecac6644ea37dd09 0.600000000000 1458467 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": 998043, "vin": [ { "gen": { "height": 998033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e7b18614e90db0a5823e7479e8da8237f387d0a3a4e7934ecac6644ea37dd09" } } ], "extra": [ 1, 233, 250, 128, 39, 36, 202, 228, 249, 149, 60, 46, 15, 65, 203, 34, 249, 120, 19, 166, 247, 113, 184, 165, 156, 116, 29, 93, 199, 155, 170, 176, 150, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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