← previous blocknext block →recent activity
Analyzing
Block #85,168,373
11 transactions · 11 stateful · 2026-07-02 18:43:51 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,168,373 · 11 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e5f2a94…4732
0x34b655…2a6f
4 touches
1 conflict
0xdf956a80…aece
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x342a12bc…c045
0x34b655…2a6f
2 touches
0 conflicts
0x3923cd2c…e6d3
0x34b655…2a6f
2 touches
0 conflicts
0x754c7f04…5673
0x34b655…2a6f
2 touches
0 conflicts
0x767a05c4…b5bd
0x34b655…2a6f
2 touches
0 conflicts
0x87210308…d018
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 0x0e5f2a945b…554732
Audit this contract →
← previous block·next block →recent activity