← previous blocknext block →recent activity
Analyzing
Block #87,587,091
19 transactions · 15 stateful · 2026-07-13 23:54:08 UTC
Parallelism
58/100
Blocked
53%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,587,091 · 19 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
3w04w15w07w18w29w310w412w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745952b2…d90c
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xbad37226…3c86
0x34b655…2a6f
6 touches
3 conflicts
0x1c503794…b0da
0x34b655…2a6f
4 touches
1 conflict
0x3560a56c…d95d
0x34b655…2a6f
4 touches
1 conflict
0x3a6290da…e683
0x34b655…2a6f
4 touches
1 conflict
0x571cb36d…3b3d
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
10 conflicts on slot 0x745952b2a0…a6d90c
Audit this contract →
← previous block·next block →recent activity