← previous blocknext block →recent activity
Analyzing
Block #87,577,016
16 transactions · 16 stateful · 2026-07-13 22:46:46 UTC
Parallelism
75/100
Blocked
19%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,577,016 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56f53fc9…46c2
0x34b655…2a6f
6 touches
3 conflicts
0xe2607c11…8fa7
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x375e887b…a361
0x34b655…2a6f
4 touches
1 conflict
0x375e887b…a362
0x34b655…2a6f
4 touches
1 conflict
0x3f7a32ad…7eca
0x34b655…2a6f
4 touches
1 conflict
0x40baaeaa…893b
0x34b655…2a6f
4 touches
1 conflict
0x6ef08b1e…eab6
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 0x56f53fc98c…4c46c2
Audit this contract →
← previous block·next block →recent activity