← previous blocknext block →recent activity
Analyzing
Block #85,194,139
16 transactions · 13 stateful · 2026-07-02 21:35:24 UTC
Parallelism
56/100
Blocked
54%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,194,139 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w114w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x234ddf93…cda5
0x34b655…2a6f
6 touches
3 conflicts
0x4384dd01…4f99
0x34b655…2a6f
6 touches
3 conflicts
0x47e0a242…75ba
0x34b655…2a6f
6 touches
3 conflicts
0x9037eb50…338c
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity