← previous blocknext block →recent activity
Analyzing
Block #87,640,954
22 transactions · 17 stateful · 2026-07-14 05:54:19 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,640,954 · 22 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
7w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xa249ae0e…1805
0x34b655…2a6f
6 touches
3 conflicts
0xd50d8366…df9d
0x34b655…2a6f
4 touches
1 conflict
0xe0af9e93…fff9
0x34b655…2a6f
4 touches
1 conflict
0x10ef891f…d725
0x34b655…2a6f
4 touches
1 conflict
0x10ef891f…d726
0x34b655…2a6f
4 touches
1 conflict
0x6519ceab…86d2
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity