← previous blocknext block →recent activity
Analyzing
Block #87,265,160
23 transactions · 19 stateful · 2026-07-12 12:00:26 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,265,160 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w411w112w514w216w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b76f967…295f
0x34b655…2a6f
6 touches
3 conflicts
0xf13d53f7…f12c
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xbcdee322…f454
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8cc1393f…07fb
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 0x4b76f967a6…28295f
Audit this contract →
← previous block·next block →recent activity