← previous blocknext block →recent activity
Analyzing
Block #95,202,642
24 transactions · 22 stateful · 2026-08-12 00:19:05 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,202,642 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w011w012w113w214w315w416w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51232c8c…f30e
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc2
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30c
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc0
0xe52b14…7230
12 touches
15 conflicts
0xf01a3cf8…9021
0xe52b14…7230
11 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0xe52b1424…bb7230
15 conflicts on slot 0x51232c8c1f…6df30e
Audit this contract →
← previous block·next block →recent activity