← previous blocknext block →recent activity
Analyzing
Block #87,577,831
22 transactions · 22 stateful · 2026-07-13 22:52:13 UTC
Parallelism
73/100
Blocked
32%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,577,831 · 22 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
4w05w16w28w39w411w515w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x68d9d4e4…91b6
0x34b655…2a6f
6 touches
3 conflicts
0x16dd4651…e88f
0x34b655…2a6f
6 touches
3 conflicts
0x78346476…4311
0x34b655…2a6f
6 touches
3 conflicts
0x2794fd34…c82f
0x34b655…2a6f
4 touches
1 conflict
0x375e887b…a361
0x34b655…2a6f
4 touches
1 conflict
0x375e887b…a362
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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity