← previous blocknext block →recent activity
Analyzing
Block #94,479,604
20 transactions · 17 stateful · 2026-08-09 11:40:01 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,479,604 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w27w08w112w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa2533cd7…8b19
0x34b655…2a6f
6 touches
3 conflicts
0x6c084dcb…640c
0x34b655…2a6f
6 touches
3 conflicts
0xf039e2f8…3d8a
0x34b655…2a6f
4 touches
1 conflict
0x2a34bb88…04d5
0x34b655…2a6f
4 touches
1 conflict
0x2a34bb88…04d6
0x34b655…2a6f
4 touches
1 conflict
0x312529c0…cd3c
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: Perpl
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity