← previous blocknext block →recent activity
Analyzing
Block #85,413,326
18 transactions · 14 stateful · 2026-07-03 21:55:26 UTC
Parallelism
72/100
Blocked
36%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,413,326 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w114w215w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe7e126…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xeccd721c…8a2e
0x34b655…2a6f
4 touches
1 conflict
0x42767e6e…020d
0x34b655…2a6f
2 touches
0 conflicts
0x4459c4a2…bed8
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
3 conflicts on slot 0x5fe7e1267e…896dd2
Audit this contract →
← previous block·next block →recent activity