← previous blocknext block →recent activity
Analyzing
Block #87,520,108
49 transactions · 41 stateful · 2026-07-13 16:25:41 UTC
Parallelism
69/100
Blocked
63%
Avg conflicts / tx
2.02
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,520,108 · 49 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w08w19w010w111w217w518w620w121w522w623w124w725w826w927w1028w229w330w432w533w634w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0xa9f8096f…f132
0x34b655…2a6f
14 touches
21 conflicts
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0x55eef346…d185
0x34b655…2a6f
10 touches
10 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
10 touches
10 conflicts
0xf5379ea4…bc3f
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity