← previous blocknext block →recent activity
Analyzing
Block #94,795,773
25 transactions · 25 stateful · 2026-08-10 14:11:44 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,795,773 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w08w19w010w111w212w013w116w218w123w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1efd6f3…a5d2
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x2840c278…bbc7
0x34b655…2a6f
6 touches
3 conflicts
0x45911da6…5523
0x34b655…2a6f
4 touches
1 conflict
0x53d526f9…1ab8
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
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 0xe1efd6f378…2ea5d2
Audit this contract →
← previous block·next block →recent activity