← previous blocknext block →recent activity
Analyzing
Block #87,738,071
22 transactions · 20 stateful · 2026-07-14 16:43:58 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,738,071 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w310w011w112w213w314w417w420w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37ee30c9…9e70
0x34b655…2a6f
10 touches
10 conflicts
0x9001f549…089d
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
8 touches
6 conflicts
0x58620f29…db5a
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
10 conflicts on slot 0x37ee30c996…d19e70
Audit this contract →
← previous block·next block →recent activity