Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca562b592c65d754ed3cda30dbb6b6a8ff5a279cb5b6a07b37749b3e025ae25b

Tx prefix hash: 0dc9c0f11dd660a9e4f87efdaca682a5d0efac173b1e76d7d8cb62a666b1846e
Tx public key: 1ac157fa3f24005e2765be62b6e024e5069f4bc0202e5a5d0f00dbafb536678a
Timestamp: 1738576385 Timestamp [UCT]: 2025-02-03 09:53:05 Age [y:d:h:m:s]: 00:287:12:12:20
Block: 1211125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203249 RingCT/type: yes/0
Extra: 011ac157fa3f24005e2765be62b6e024e5069f4bc0202e5a5d0f00dbafb536678a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a7d815ab76aac888fa1bd0b2b69408645d9ab448dce78710b50f50dec37004d 0.600000000000 1697884 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": 1211135, "vin": [ { "gen": { "height": 1211125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a7d815ab76aac888fa1bd0b2b69408645d9ab448dce78710b50f50dec37004d" } } ], "extra": [ 1, 26, 193, 87, 250, 63, 36, 0, 94, 39, 101, 190, 98, 182, 224, 36, 229, 6, 159, 75, 192, 32, 46, 90, 93, 15, 0, 219, 175, 181, 54, 103, 138, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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