← previous blocknext block →recent activity
Analyzing
Block #87,489,594
17 transactions · 15 stateful · 2026-07-13 13:01:15 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,489,594 · 17 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
1w02w17w08w19w211w112w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0x88adad52…54b7
0x34b655…2a6f
8 touches
6 conflicts
0x2da7072a…5386
0x34b655…2a6f
4 touches
1 conflict
0x56b580bf…f969
0x34b655…2a6f
4 touches
1 conflict
0x61757a59…d89f
0x34b655…2a6f
4 touches
1 conflict
0x6f9c6bd9…c66c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
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 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity