← previous blocknext block →recent activity
Analyzing
Block #85,107,346
8 transactions · 7 stateful · 2026-07-02 11:56:37 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,107,346 · 8 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa16b3e4e…0786
0x34b655…2a6f
4 touches
1 conflict
0xa16b3e4e…0787
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x60b0789f…d90a
0x34b655…2a6f
3 touches
1 conflict
0xbfecf1a6…4764
0x34b655…2a6f
3 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
2 touches
0 conflicts
0xa4658f5c…b257
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 0xa16b3e4e62…240786
Audit this contract →
← previous block·next block →recent activity