← previous blocknext block →recent activity
Analyzing
Block #85,248,372
23 transactions · 18 stateful · 2026-07-03 03:36:41 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,248,372 · 23 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
5w06w07w18w210w011w112w313w015w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9cf2d0bf…8d46
0x34b655…2a6f
4 touches
1 conflict
0xb0986ca3…c05d
0x34b655…2a6f
4 touches
1 conflict
0xd597209e…9800
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x280a9762…2db6
0x34b655…2a6f
4 touches
1 conflict
0x42efa1e9…7433
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
1 conflict on slot 0x9cf2d0bf82…a78d46
Audit this contract →
← previous block·next block →recent activity