← previous blocknext block →recent activity
Analyzing
Block #85,129,008
16 transactions · 15 stateful · 2026-07-02 14:21:31 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,129,008 · 16 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
1w03w16w111w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e507257…71c1
0x34b655…2a6f
6 touches
3 conflicts
0x67d8b378…f2f8
0x34b655…2a6f
6 touches
3 conflicts
0x7b3f8378…b37d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
4 touches
1 conflict
0xfe83ed1d…f9ca
0x34b655…2a6f
4 touches
1 conflict
0x9457fb68…fec9
0x34b655…2a6f
4 touches
1 conflict
0xac6f24e7…c98b
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 0x8e50725790…b871c1
Audit this contract →
← previous block·next block →recent activity