← previous blocknext block →recent activity
Analyzing
Block #85,616,151
8 transactions · 7 stateful · 2026-07-04 20:25:50 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,616,151 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7f7d98f…cfe7
0x34b655…2a6f
4 touches
1 conflict
0xe40ce249…a28c
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc7f7d98fdd…77cfe7
Audit this contract →
← previous block·next block →recent activity