← previous blocknext block →recent activity
Analyzing
Block #87,733,744
21 transactions · 21 stateful · 2026-07-14 16:15:02 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,733,744 · 21 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
1w02w13w25w06w17w28w310w011w312w116w417w219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4de6652…13f4
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x201679bc…0414
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x58620f29…db5a
0x34b655…2a6f
8 touches
6 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
8 touches
6 conflicts
0xac6f24e7…c98b
0x34b655…2a6f
8 touches
6 conflicts
0xc1365881…e725
0xd32edf…ff58
7 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 0xc4de665222…6513f4
Audit this contract →
← previous block·next block →recent activity