← previous blocknext block →recent activity
Analyzing
Block #85,134,554
25 transactions · 23 stateful · 2026-07-02 14:58:34 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,134,554 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w112w013w114w217w218w319w420w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xcc6e2e88…6569
0x34b655…2a6f
6 touches
3 conflicts
0x9385d07d…4829
0x34b655…2a6f
6 touches
3 conflicts
0x3fde350e…8d43
0x34b655…2a6f
4 touches
1 conflict
0x43e2eda1…396f
0x34b655…2a6f
4 touches
1 conflict
0x52245372…ad6b
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity