← previous blocknext block →recent activity
Analyzing
Block #87,442,936
10 transactions · 10 stateful · 2026-07-13 07:49:15 UTC
Parallelism
60/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,442,936 · 10 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
1w02w13w27w3
- 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
0x7071bb5a…522a
0x34b655…2a6f
4 touches
1 conflict
0xcedede42…ce2d
0x34b655…2a6f
4 touches
1 conflict
0xea3e9ed9…5ac7
0x34b655…2a6f
4 touches
1 conflict
0x4b0a67ef…b8ba
0x34b655…2a6f
4 touches
1 conflict
0xf2fc1fab…45e9
0x34b655…2a6f
4 touches
1 conflict
0x40080907…45cc
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