← previous blocknext block →recent activity
Analyzing
Block #87,589,921
20 transactions · 16 stateful · 2026-07-14 00:13:05 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,589,921 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w29w110w211w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacb6de83…d893
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0f15f74f…8d71
0x34b655…2a6f
4 touches
1 conflict
0x0f15f74f…8d72
0x34b655…2a6f
4 touches
1 conflict
0x1737ef68…1e55
0x34b655…2a6f
4 touches
1 conflict
0x56f7a389…74fd
0x34b655…2a6f
4 touches
1 conflict
0x671886b7…46fe
0x34b655…2a6f
4 touches
1 conflict
0x689d5e98…d068
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
3 conflicts on slot 0xacb6de838e…12d893
Audit this contract →
← previous block·next block →recent activity