← previous blocknext block →recent activity
Analyzing
Block #85,133,258
23 transactions · 21 stateful · 2026-07-02 14:49:57 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,133,258 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w19w210w312w113w014w119w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x765cd07a…1018
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49e8c10c…78a8
0x34b655…2a6f
4 touches
1 conflict
0x570a7d4c…dec5
0x34b655…2a6f
4 touches
1 conflict
0x7b3da897…b268
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0x9495bffc…46e6
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
3 conflicts on slot 0x765cd07a13…531018
Audit this contract →
← previous block·next block →recent activity