← previous blocknext block →recent activity
Analyzing
Block #87,524,195
17 transactions · 17 stateful · 2026-07-13 16:53:20 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,524,195 · 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
1w02w14w05w16w27w312w013w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xdfe79b9a…715a
0x34b655…2a6f
6 touches
3 conflicts
0x17b720f5…ad7a
0x34b655…2a6f
4 touches
1 conflict
0x4b628349…f327
0x34b655…2a6f
4 touches
1 conflict
0x4e10224d…58d3
0x34b655…2a6f
4 touches
1 conflict
0x4e1ce17e…98a7
0x34b655…2a6f
4 touches
1 conflict
0x69ee34d1…30f8
0x34b655…2a6f
4 touches
1 conflict
0x6f7baf78…77a9
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity