← previous blocknext block →recent activity
Analyzing
Block #87,589,954
21 transactions · 18 stateful · 2026-07-14 00:13:18 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,589,954 · 21 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
1w04w08w19w210w111w312w414w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacb6de83…d893
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf039e2f8…3d8a
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x67c5013f…c1fc
0x34b655…2a6f
4 touches
1 conflict
0x8b87ece6…3353
0x34b655…2a6f
4 touches
1 conflict
0x92db1e96…68d4
0x34b655…2a6f
4 touches
1 conflict
0xa0237ed3…2622
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 0xacb6de838e…12d893
Audit this contract →
← previous block·next block →recent activity