← previous blocknext block →recent activity
Analyzing
Block #85,994,710
26 transactions · 19 stateful · 2026-07-06 14:29:16 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,994,710 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w013w014w015w116w117w121w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79b3209b…f766
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa7a1d036…b8aa
0x34b655…2a6f
6 touches
3 conflicts
0x080ec687…da80
0x34b655…2a6f
4 touches
1 conflict
0x1e133356…1a95
0x34b655…2a6f
4 touches
1 conflict
0x3824aec1…b2c0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7012e9c1…f525
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 0x79b3209b12…57f766
Audit this contract →
← previous block·next block →recent activity