← previous blocknext block →recent activity
Analyzing
Block #87,706,121
23 transactions · 20 stateful · 2026-07-14 13:10:04 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,706,121 · 23 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
1w04w16w07w18w211w012w113w214w316w018w420w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388114fc…db6d
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xee7aa362…7109
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2a967872…3466
0x34b655…2a6f
4 touches
1 conflict
0x388114fc…db6c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa38eb2fc…1659
0x34b655…2a6f
4 touches
1 conflict
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 0x388114fca1…98db6d
Audit this contract →
← previous block·next block →recent activity