← previous blocknext block →recent activity
Analyzing
Block #85,130,512
24 transactions · 22 stateful · 2026-07-02 14:31:35 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,130,512 · 24 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
2w03w04w16w27w38w49w010w111w212w317w120w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x04d56766…749e
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x5b353877…605d
0x34b655…2a6f
6 touches
3 conflicts
0xcf683477…c981
0x34b655…2a6f
6 touches
3 conflicts
0xa4723ee3…8c11
0x34b655…2a6f
6 touches
3 conflicts
0xf2112d98…bb04
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
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: 0x04fdeac2…f747d7
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity