← previous blocknext block →recent activity
Analyzing
Block #85,565,565
22 transactions · 20 stateful · 2026-07-04 14:48:58 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,565,565 · 22 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
1w04w18w09w010w111w212w314w115w117w419w020w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b2f3e6d…978f
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
6 touches
3 conflicts
0x30c5329c…711c
0x34b655…2a6f
6 touches
3 conflicts
0x74f7ff0d…67ee
0x34b655…2a6f
6 touches
3 conflicts
0x0490e695…7c53
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x65b4cee3…2f18
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
6 conflicts on slot 0x7b2f3e6d7d…4d978f
Audit this contract →
← previous block·next block →recent activity