← previous blocknext block →recent activity
Analyzing
Block #87,496,910
35 transactions · 32 stateful · 2026-07-13 13:50:12 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
1.94
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,496,910 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w18w09w110w011w112w213w314w415w516w617w720w622w723w125w828w130w231w232w733w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x7b2f3e6d…978f
0x34b655…2a6f
12 touches
15 conflicts
0x4c188934…158e
0x34b655…2a6f
12 touches
15 conflicts
0xfdd655b8…bf89
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xc2db6e7a…d074
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd2b87a88…aa57
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity