← previous blocknext block →recent activity
Analyzing
Block #85,768,207
12 transactions · 11 stateful · 2026-07-05 13:19:31 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,768,207 · 12 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
1w02w14w05w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x9605757b…9ba5
0x40c49f…2af0
2 touches
0 conflicts
0xec7d10d5…4678
0x40c49f…2af0
2 touches
0 conflicts
0x2f74f175…9284
0x69df8a…6292
2 touches
0 conflicts
0x2f74f175…9285
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 0x58620f2942…18db5a
Audit this contract →
← previous block·next block →recent activity