← previous blocknext block →recent activity
Analyzing
Block #85,874,542
19 transactions · 14 stateful · 2026-07-06 01:07:44 UTC
Parallelism
68/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,874,542 · 19 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
4w010w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb56f0740…7542
0x34b655…2a6f
6 touches
3 conflicts
0x3d1f0f09…f4a1
0x34b655…2a6f
4 touches
1 conflict
0x41268521…4245
0x34b655…2a6f
4 touches
1 conflict
0x50bf62b5…99b6
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x652bc0f0…6faf
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity