← previous blocknext block →recent activity
Analyzing
Block #85,628,257
9 transactions · 9 stateful · 2026-07-04 21:46:26 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,628,257 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2d7e60b7…c173
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x178db37f…debb
0x34b655…2a6f
4 touches
1 conflict
0xef02ed46…48a4
0x34b655…2a6f
3 touches
1 conflict
0x006c3b86…59a9
0x34b655…2a6f
2 touches
0 conflicts
0x00966e54…7d1d
0x34b655…2a6f
2 touches
0 conflicts
0x036e7d45…7d9d
0x34b655…2a6f
2 touches
0 conflicts
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity