← previous blocknext block →recent activity
Analyzing
Block #87,793,588
14 transactions · 13 stateful · 2026-07-14 22:55:21 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1.14
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,793,588 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w48w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9465204c…bf37
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x28c62bca…b746
0x34b655…2a6f
10 touches
10 conflicts
0xd19c9d38…b459
0x34b655…2a6f
10 touches
10 conflicts
0x9ae859db…2d84
0x34b655…2a6f
10 touches
10 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x9465204cd8…debf37
Audit this contract →
← previous block·next block →recent activity