← previous blocknext block →recent activity
Analyzing
Block #85,540,803
24 transactions · 19 stateful · 2026-07-04 12:04:06 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,540,803 · 24 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
1w03w04w19w010w011w113w115w120w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca0f0668…caf3
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x30faf03c…78b1
0x34b655…2a6f
4 touches
1 conflict
0x33e3dcdd…1f1f
0x34b655…2a6f
4 touches
1 conflict
0x4d8a8821…df85
0x34b655…2a6f
4 touches
1 conflict
0x62341e2a…2d78
0x34b655…2a6f
4 touches
1 conflict
0xafb2524a…0ce4
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity