← previous blocknext block →recent activity
Analyzing
Block #87,665,289
21 transactions · 17 stateful · 2026-07-14 08:36:55 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,665,289 · 21 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
2w03w14w05w16w210w312w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x10fec71b…e12f
0x34b655…2a6f
4 touches
1 conflict
0x17c70f19…23a7
0x34b655…2a6f
4 touches
1 conflict
0x20a110e8…918d
0x34b655…2a6f
4 touches
1 conflict
0x21158693…63e2
0x34b655…2a6f
4 touches
1 conflict
0x35149630…ef8a
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity