← previous blocknext block →recent activity
Analyzing
Block #87,052,464
10 transactions · 8 stateful · 2026-07-11 12:18:08 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,052,464 · 10 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38b61269…48d7
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x1951ee47…540f
0x34b655…2a6f
2 touches
0 conflicts
0x727fbce7…0c80
0x34b655…2a6f
2 touches
0 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
2 touches
0 conflicts
0x83a6cd6a…91c7
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 0x38b61269d3…c048d7
Audit this contract →
← previous block·next block →recent activity