← previous blocknext block →recent activity
Analyzing
Block #87,793,240
16 transactions · 16 stateful · 2026-07-14 22:53:02 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,793,240 · 16 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
3w04w15w26w37w08w010w411w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd19c9d38…b459
0x34b655…2a6f
8 touches
6 conflicts
0x9465204c…bf37
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x28c62bca…b746
0x34b655…2a6f
8 touches
6 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
7 touches
6 conflicts
0x26763d4e…651f
0x34b655…2a6f
6 touches
3 conflicts
0x9ae859db…2d84
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
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
6 conflicts on slot 0xd19c9d382e…d4b459
Audit this contract →
← previous block·next block →recent activity