← previous blocknext block →recent activity
Analyzing
Block #87,793,547
16 transactions · 14 stateful · 2026-07-14 22:55:05 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
1.81
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,793,547 · 16 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
3w04w15w26w37w48w59w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9465204c…bf37
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 conflicts
0x28c62bca…b746
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x98834cc0…6c23
0x34b655…2a6f
14 touches
21 conflicts
0x9ae859db…2d84
0x34b655…2a6f
14 touches
21 conflicts
0xb59b0c85…f36c
0x34b655…2a6f
14 touches
21 conflicts
0x739f9ee7…3a3d
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
28 conflicts on slot 0x9465204cd8…debf37
Audit this contract →
← previous block·next block →recent activity