← previous blocknext block →recent activity
Analyzing
Block #86,239,260
14 transactions · 9 stateful · 2026-07-07 17:41:48 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,239,260 · 14 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
5w06w18w210w311w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80033ffa…f6d3
0x34b655…2a6f
6 touches
3 conflicts
0xd8bc53a3…c2fe
0x34b655…2a6f
6 touches
3 conflicts
0xbd9491f7…dd92
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x92b49f44…ee4f
0x34b655…2a6f
4 touches
1 conflict
0xbfa73fac…6fff
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
3 conflicts on slot 0x80033ffaf1…dff6d3
Audit this contract →
← previous block·next block →recent activity