← previous blocknext block →recent activity
Analyzing
Block #85,576,279
27 transactions · 18 stateful · 2026-07-04 16:00:18 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,576,279 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w08w19w210w011w013w121w022w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x8c84e7fe…afbd
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x05edf2cf…ac3c
0x34b655…2a6f
4 touches
1 conflict
0x262c8ec3…d8f9
0x34b655…2a6f
4 touches
1 conflict
0x2a9a8ccd…df4d
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
6 conflicts on slot 0xefcdf19725…1096a2
Audit this contract →
← previous block·next block →recent activity