← previous blocknext block →recent activity
Analyzing
Block #87,734,188
17 transactions · 16 stateful · 2026-07-14 16:18:00 UTC
Parallelism
65/100
Blocked
31%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,734,188 · 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
4w05w18w09w210w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa55c4598…2988
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x26a7454d…895b
0x34b655…2a6f
4 touches
1 conflict
0x28c62bca…b746
0x34b655…2a6f
4 touches
1 conflict
0x4fa747b5…f843
0x34b655…2a6f
4 touches
1 conflict
0x56f6adae…573c
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
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
3 conflicts on slot 0xa55c45989b…e52988
Audit this contract →
← previous block·next block →recent activity