← previous blocknext block →recent activity
Analyzing
Block #87,131,316
11 transactions · 9 stateful · 2026-07-11 21:04:47 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,131,316 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x072f36ce…7ecf
0x34b655…2a6f
4 touches
1 conflict
0x99c00c45…c701
0x34b655…2a6f
4 touches
1 conflict
0xd5ab2f5b…092b
0x34b655…2a6f
4 touches
1 conflict
0xdbf50b38…ac8c
0x34b655…2a6f
4 touches
1 conflict
0x0586db65…e6c4
0x34b655…2a6f
2 touches
0 conflicts
0x0a2ac8c0…8b3c
0x34b655…2a6f
2 touches
0 conflicts
0x0f9828f0…3358
0x34b655…2a6f
2 touches
0 conflicts
0x1745a13c…f989
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x072f36ce8f…257ecf
Audit this contract →
← previous block·next block →recent activity