← previous blocknext block →recent activity
Analyzing
Block #87,793,314
23 transactions · 21 stateful · 2026-07-14 22:53:32 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,793,314 · 23 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
5w06w17w211w012w113w315w416w520w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9465204c…bf37
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xe2ce91e2…b99e
0x34b655…2a6f
8 touches
6 conflicts
0x4be0b838…9dd7
0x34b655…2a6f
8 touches
6 conflicts
0x9ae859db…2d84
0x34b655…2a6f
8 touches
6 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x26050074…6967
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
15 conflicts on slot 0x9465204cd8…debf37
Audit this contract →
← previous block·next block →recent activity