Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebbda873a57bd2df6e25ff9afd8a06cfe591dc29080c8e95989cc1f60908a9f4

Tx prefix hash: a231411ca93f4baeb094cf8787b6ad895fed1ec89d15b018ad027ab561b9a98c
Tx public key: c2fe076101f6405a84506d23d879ecfb27b03ed5f3312ea2a4ebaf56ab121f2b
Timestamp: 1736552583 Timestamp [UCT]: 2025-01-10 23:43:03 Age [y:d:h:m:s]: 00:060:11:21:43
Block: 1194636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43014 RingCT/type: yes/0
Extra: 01c2fe076101f6405a84506d23d879ecfb27b03ed5f3312ea2a4ebaf56ab121f2b0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2758e0a143868ac01c18c4396f0a3df2fba4b24d81626e0b8c23d5f985d00e8 0.600000000000 1681213 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": 1194646, "vin": [ { "gen": { "height": 1194636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2758e0a143868ac01c18c4396f0a3df2fba4b24d81626e0b8c23d5f985d00e8" } } ], "extra": [ 1, 194, 254, 7, 97, 1, 246, 64, 90, 132, 80, 109, 35, 216, 121, 236, 251, 39, 176, 62, 213, 243, 49, 46, 162, 164, 235, 175, 86, 171, 18, 31, 43, 2, 17, 0, 0, 0, 5, 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