← previous blocknext block →recent activity
Analyzing
Block #87,698,506
18 transactions · 17 stateful · 2026-07-14 12:18:52 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,698,506 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w07w110w212w213w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xa243ce39…3ff4
0x34b655…2a6f
6 touches
3 conflicts
0x32dfa6a9…12f6
0x34b655…2a6f
4 touches
1 conflict
0x3d22c439…de6d
0x34b655…2a6f
4 touches
1 conflict
0x44063a0c…a912
0x34b655…2a6f
4 touches
1 conflict
0x4940bb84…4ec2
0x34b655…2a6f
4 touches
1 conflict
0x4f51d069…d0b4
0x34b655…2a6f
4 touches
1 conflict
0x659bb236…9438
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity