← previous blocknext block →recent activity
Analyzing
Block #87,793,103
18 transactions · 18 stateful · 2026-07-14 22:52:07 UTC
Parallelism
39/100
Blocked
67%
Avg conflicts / tx
2.56
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,793,103 · 18 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w48w59w611w214w716w917w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9465204c…bf37
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x9ae859db…2d84
0x34b655…2a6f
12 touches
15 conflicts
0x28c62bca…b746
0x34b655…2a6f
12 touches
15 conflicts
0x805d08cf…3cfc
0x34b655…2a6f
12 touches
15 conflicts
0x3726966a…669d
0x34b655…2a6f
11 touches
15 conflicts
0x7aad02c6…b979
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
28 conflicts on slot 0x9465204cd8…debf37
Audit this contract →
← previous block·next block →recent activity