← previous blocknext block →recent activity
Analyzing
Block #85,511,276
19 transactions · 17 stateful · 2026-07-04 08:47:28 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,511,276 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w114w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb1939b09…99dd
0x34b655…2a6f
6 touches
3 conflicts
0xa7396f51…7f2f
0x34b655…2a6f
5 touches
3 conflicts
0x3e505a15…70f8
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
0x34b655…2a6f
4 touches
1 conflict
0x6bd79c06…6d09
0x34b655…2a6f
4 touches
1 conflict
0x7375de93…7ee0
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
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