← previous blocknext block →recent activity
Analyzing
Block #86,989,501
13 transactions · 12 stateful · 2026-07-11 05:17:28 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,989,501 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w08w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x29ba8cb6…dcee
0x34b655…2a6f
4 touches
1 conflict
0x755fc221…afae
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0490581d…adaf
0x34b655…2a6f
2 touches
0 conflicts
0x25bece3e…42e2
0x34b655…2a6f
2 touches
0 conflicts
0x3adc4a83…09bc
0x34b655…2a6f
2 touches
0 conflicts
0x3bdd71a2…b6eb
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity