← previous blocknext block →recent activity
Analyzing
Block #87,455,160
22 transactions · 19 stateful · 2026-07-13 09:11:01 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,455,160 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w39w410w311w412w413w214w518w419w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0446875…2b96
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x9b02ba92…7100
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x4ab0fef9…caef
0x34b655…2a6f
4 touches
1 conflict
0x4f473983…7d27
0x34b655…2a6f
4 touches
1 conflict
0x5ad347dc…ff16
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xb04468752d…352b96
Audit this contract →
← previous block·next block →recent activity