← previous blocknext block →recent activity
Analyzing
Block #85,108,166
11 transactions · 11 stateful · 2026-07-02 12:02:06 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,108,166 · 11 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
1w02w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05b1b07a…7a99
0x34b655…2a6f
4 touches
1 conflict
0x16a05dbf…0d3a
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x65d2962c…8b87
0x34b655…2a6f
4 touches
1 conflict
0x6c2aa5be…d808
0x34b655…2a6f
4 touches
1 conflict
0x79b3209b…f766
0x34b655…2a6f
4 touches
1 conflict
0x9b8b9078…0785
0x34b655…2a6f
4 touches
1 conflict
0x9eb155db…f714
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 0x05b1b07aba…747a99
Audit this contract →
← previous block·next block →recent activity