← previous blocknext block →recent activity
Analyzing
Block #94,751,722
24 transactions · 22 stateful · 2026-08-10 10:29:55 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,751,722 · 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
4w05w16w07w110w211w313w417w018w120w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x3fc40870…7ef4
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x59a54ff4…d21b
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x862ac33e…15a3
0x34b655…2a6f
4 touches
1 conflict
0x9e9ffe69…e039
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
15 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity