Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3e86f6e30d2db7b8a2d24a8f79a4d56a6dd3ff1b0c2080f4038eb9ae002568d

Tx prefix hash: b02e35db67f369e0567862e5712e746883822054e630373738a1ab43e8276904
Tx public key: db0a19beb3c6aca8733a83ed30fac2a6318629acdef7a96a1ae2fbe273e00105
Timestamp: 1742430924 Timestamp [UCT]: 2025-03-20 00:35:24 Age [y:d:h:m:s]: 00:289:03:07:11
Block: 1243061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204430 RingCT/type: yes/0
Extra: 01db0a19beb3c6aca8733a83ed30fac2a6318629acdef7a96a1ae2fbe273e00105021100000005ed95dce7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16dccf4c95e6af94439973b8ad045ea896f863af0ee0696602a57862e3c48df6 0.600000000000 1730046 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": 1243071, "vin": [ { "gen": { "height": 1243061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16dccf4c95e6af94439973b8ad045ea896f863af0ee0696602a57862e3c48df6" } } ], "extra": [ 1, 219, 10, 25, 190, 179, 198, 172, 168, 115, 58, 131, 237, 48, 250, 194, 166, 49, 134, 41, 172, 222, 247, 169, 106, 26, 226, 251, 226, 115, 224, 1, 5, 2, 17, 0, 0, 0, 5, 237, 149, 220, 231, 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