← previous blocknext block →recent activity
Analyzing
Block #86,957,445
9 transactions · 8 stateful · 2026-07-11 01:43:16 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,957,445 · 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
1w04w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1db601b…c70d
0x34b655…2a6f
4 touches
1 conflict
0xa412324b…90aa
0x34b655…2a6f
4 touches
1 conflict
0xa412324b…90ab
0x34b655…2a6f
4 touches
1 conflict
0xae8ff4a3…733f
0x34b655…2a6f
4 touches
1 conflict
0xba18b403…57a1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
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
1 conflict on slot 0xd1db601beb…bcc70d
Audit this contract →
← previous block·next block →recent activity