← previous blocknext block →recent activity
Analyzing
Block #87,499,360
24 transactions · 20 stateful · 2026-07-13 14:06:36 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,499,360 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w19w210w314w415w516w617w722w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7b2f3e6d…978f
0x34b655…2a6f
8 touches
6 conflicts
0x6a4868a5…367e
0x34b655…2a6f
8 touches
6 conflicts
0x5d2c01c7…439f
0x34b655…2a6f
8 touches
6 conflicts
0xe9530981…e4cb
0x34b655…2a6f
6 touches
3 conflicts
0x41fc2b04…2805
0x34b655…2a6f
6 touches
3 conflicts
0x4b628349…f327
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity