← previous blocknext block →recent activity
Analyzing
Block #85,612,282
16 transactions · 15 stateful · 2026-07-04 20:00:07 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,612,282 · 16 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
6w07w09w112w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5eb187dd…b1d6
0x34b655…2a6f
4 touches
1 conflict
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xeccd721c…8a2e
0x34b655…2a6f
4 touches
1 conflict
0xef02ed46…48a4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xb05cd4f5…73d0
0x69df8a…6292
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 0x5eb187dd4c…a6b1d6
Audit this contract →
← previous block·next block →recent activity