← previous blocknext block →recent activity
Analyzing
Block #85,785,667
10 transactions · 9 stateful · 2026-07-05 15:15:49 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,785,667 · 10 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x002dfab7…aa48
0x34b655…2a6f
2 touches
0 conflicts
0x0a3e6af7…5de9
0x34b655…2a6f
2 touches
0 conflicts
0x10c9dff3…8ea4
0x34b655…2a6f
2 touches
0 conflicts
0x1c0d9042…ba4a
0x34b655…2a6f
2 touches
0 conflicts
0x22f55465…3968
0x34b655…2a6f
2 touches
0 conflicts
0x330bae15…e1f7
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity