← previous blocknext block →recent activity
Analyzing
Block #87,122,648
9 transactions · 8 stateful · 2026-07-11 20:06:53 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,122,648 · 9 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
1w02w14w25w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xe5359847…8a97
0x34b655…2a6f
4 touches
1 conflict
0xae10c461…db87
0x34b655…2a6f
4 touches
1 conflict
0xb784e5ed…fb82
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbd1c6f7e…6728
0x34b655…2a6f
4 touches
1 conflict
0xd5ab2f5b…092b
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity