← previous blocknext block →recent activity
Analyzing
Block #87,667,986
14 transactions · 13 stateful · 2026-07-14 08:54:55 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,667,986 · 14 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
2w03w14w26w09w110w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x106f5133…b723
0x34b655…2a6f
8 touches
6 conflicts
0x4e1ce17e…98a7
0x34b655…2a6f
6 touches
3 conflicts
0x24d68cf2…09b7
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0x1bd6042e…fa9b
0x34b655…2a6f
4 touches
1 conflict
0x20a110e8…918d
0x34b655…2a6f
4 touches
1 conflict
0x21158693…63e2
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 0x106f5133c5…d6b723
Audit this contract →
← previous block·next block →recent activity