Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4515ff2649bab4309b1776ca0b119028c803786da56834e287a1611559e372fe

Tx prefix hash: b3dd48c3e2715295ef2bc0d170636d595686d26b8a82845f6d051def1a3c36b8
Tx public key: 25e6f9798f62f2693b6722b862d6c036420b80cc809dad2986cb595bac1dfa42
Timestamp: 1755621281 Timestamp [UCT]: 2025-08-19 16:34:41 Age [y:d:h:m:s]: 00:092:12:12:49
Block: 1349986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66024 RingCT/type: yes/0
Extra: 0125e6f9798f62f2693b6722b862d6c036420b80cc809dad2986cb595bac1dfa42021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a89c0d97a8f36e9e0d0dcc587c7a3b664e6a6d5edd5282a01cfd079b51f302b 0.600000000000 1837925 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": 1349996, "vin": [ { "gen": { "height": 1349986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a89c0d97a8f36e9e0d0dcc587c7a3b664e6a6d5edd5282a01cfd079b51f302b" } } ], "extra": [ 1, 37, 230, 249, 121, 143, 98, 242, 105, 59, 103, 34, 184, 98, 214, 192, 54, 66, 11, 128, 204, 128, 157, 173, 41, 134, 203, 89, 91, 172, 29, 250, 66, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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