← previous blocknext block →recent activity
Analyzing
Block #87,786,025
18 transactions · 16 stateful · 2026-07-14 22:04:47 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,786,025 · 18 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
1w03w14w25w36w47w58w69w214w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x9001f549…089d
0x34b655…2a6f
10 touches
10 conflicts
0x9ae859db…2d84
0x34b655…2a6f
8 touches
6 conflicts
0x28c62bca…b746
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x9910eda8…2ed1
0x34b655…2a6f
8 touches
6 conflicts
0xeed1124d…6a86
0x34b655…2a6f
8 touches
6 conflicts
0xb96a99db…95aa
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity