Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f2fa63458e19b40f9e2c9743dd8326d9dc14e7ee40ea0ba7a088a7ae8c560d0

Tx prefix hash: 470ac5069cbd1cf3a5a63ea5b27bcf8a4106bf7adc9af3804c7cb5c981a63408
Tx public key: 92b9a96883047c86e120f7bd0a7e8bcb477078b0425e0a3e99b9e4c8f59f44db
Timestamp: 1712752539 Timestamp [UCT]: 2024-04-10 12:35:39 Age [y:d:h:m:s]: 00:288:22:59:34
Block: 997444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206811 RingCT/type: yes/0
Extra: 0192b9a96883047c86e120f7bd0a7e8bcb477078b0425e0a3e99b9e4c8f59f44db0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81f4ce33d14e2e7fed8fc59e130f006448ee96d1ac7c441df193e61dd0441afe 0.600000000000 1457876 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": 997454, "vin": [ { "gen": { "height": 997444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81f4ce33d14e2e7fed8fc59e130f006448ee96d1ac7c441df193e61dd0441afe" } } ], "extra": [ 1, 146, 185, 169, 104, 131, 4, 124, 134, 225, 32, 247, 189, 10, 126, 139, 203, 71, 112, 120, 176, 66, 94, 10, 62, 153, 185, 228, 200, 245, 159, 68, 219, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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