← previous blocknext block →recent activity
Analyzing
Block #87,756,231
9 transactions · 8 stateful · 2026-07-14 18:45:25 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,756,231 · 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
1w02w13w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x08547d8c…14ff
0x34b655…2a6f
6 touches
3 conflicts
0xf8c9546a…ebba
0x34b655…2a6f
4 touches
1 conflict
0xa4bfee65…e0f6
0x34b655…2a6f
4 touches
1 conflict
0xbc9f3343…14fb
0x34b655…2a6f
4 touches
1 conflict
0xc6bb7e6c…bf35
0x34b655…2a6f
4 touches
1 conflict
0xda16e95c…521b
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