← previous blocknext block →recent activity
Analyzing
Block #86,968,611
13 transactions · 11 stateful · 2026-07-11 02:57:56 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,968,611 · 13 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
5w06w07w09w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9d235e0…3a44
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xe2ce91e2…b99e
0x34b655…2a6f
4 touches
1 conflict
0xe9d235e0…3a43
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0e5211d5…fbfe
0x34b655…2a6f
4 touches
1 conflict
0x30aaa982…9d53
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xe9d235e02e…9b3a44
Audit this contract →
← previous block·next block →recent activity