← previous blocknext block →recent activity
Analyzing
Block #85,181,308
26 transactions · 21 stateful · 2026-07-02 20:10:00 UTC
Parallelism
77/100
Blocked
43%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,181,308 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w111w012w113w214w315w416w518w219w223w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x6d952553…8747
0x34b655…2a6f
6 touches
3 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
6 touches
3 conflicts
0x801058a8…5bc3
0x34b655…2a6f
6 touches
3 conflicts
0xd2a592d9…1a96
0x34b655…2a6f
6 touches
3 conflicts
0xe732567d…b65d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity