Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f53414edeba234b7480993100a5c02f9bd580ffa98e200c422e69e7de2dc7b

Tx prefix hash: ebd573cfcc28f536c2453098fda91fd5257d3a6fbc9954f42527a742d44d6da1
Tx public key: 4393dd3ac708c733635a0cf503a8b4c22d18e853a539fcdafe3e4ab09ff5c8c9
Timestamp: 1744764202 Timestamp [UCT]: 2025-04-16 00:43:22 Age [y:d:h:m:s]: 00:262:19:14:30
Block: 1262354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185628 RingCT/type: yes/0
Extra: 014393dd3ac708c733635a0cf503a8b4c22d18e853a539fcdafe3e4ab09ff5c8c9021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7466e2806bc0e4af62e58d45144048d407c08a941165075975dc42f23574499 0.600000000000 1749533 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": 1262364, "vin": [ { "gen": { "height": 1262354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7466e2806bc0e4af62e58d45144048d407c08a941165075975dc42f23574499" } } ], "extra": [ 1, 67, 147, 221, 58, 199, 8, 199, 51, 99, 90, 12, 245, 3, 168, 180, 194, 45, 24, 232, 83, 165, 57, 252, 218, 254, 62, 74, 176, 159, 245, 200, 201, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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