← previous blocknext block →recent activity
Analyzing
Block #85,911,059
30 transactions · 24 stateful · 2026-07-06 05:11:02 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,911,059 · 30 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
1w02w14w05w16w27w39w010w112w213w214w021w327w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f900be0…cd6e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xbdc80bf7…e947
0x34b655…2a6f
8 touches
6 conflicts
0x91220b8f…7a02
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
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
6 conflicts on slot 0x6f900be04d…4ccd6e
Audit this contract →
← previous block·next block →recent activity