← previous blocknext block →recent activity
Analyzing
Block #87,723,827
22 transactions · 17 stateful · 2026-07-14 15:08:40 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,723,827 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w07w18w210w311w212w413w017w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa55aabd7…cdfd
0x34b655…2a6f
8 touches
6 conflicts
0x5ec64628…72e4
0x34b655…2a6f
8 touches
6 conflicts
0xf549aab8…3c09
0x34b655…2a6f
6 touches
3 conflicts
0xf4713590…d750
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x07fc7174…a4c5
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
6 conflicts on slot 0xa55aabd704…3ccdfd
Audit this contract →
← previous block·next block →recent activity