← previous blocknext block →recent activity
Analyzing
Block #87,725,052
16 transactions · 15 stateful · 2026-07-14 15:16:52 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,725,052 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w18w212w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa0485cc…0700
0x34b655…2a6f
4 touches
1 conflict
0xc9dce17a…a1a1
0x34b655…2a6f
4 touches
1 conflict
0xca608d0c…f23b
0x34b655…2a6f
4 touches
1 conflict
0xd6d13693…e80e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x10cab052…8d64
0x34b655…2a6f
4 touches
1 conflict
0x2f35c56f…046b
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
1 conflict on slot 0xfa0485cc98…250700
Audit this contract →
← previous block·next block →recent activity