← previous blocknext block →recent activity
Analyzing
Block #87,878,564
22 transactions · 14 stateful · 2026-07-15 08:23:42 UTC
Parallelism
77/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,878,564 · 22 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
2w06w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xd972ea45…48b5
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x514e11a0…a09b
0x34b655…2a6f
4 touches
1 conflict
0x78346476…4311
0x34b655…2a6f
4 touches
1 conflict
0x7d7ff6bb…f729
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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity