← previous blocknext block →recent activity
Analyzing
Block #85,146,312
21 transactions · 17 stateful · 2026-07-02 16:17:00 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,146,312 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w07w18w211w216w117w219w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3fbc9b8…ab58
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x30153288…6d46
0x34b655…2a6f
6 touches
3 conflicts
0x43e2eda1…396f
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x7239ee57…7b05
0x34b655…2a6f
4 touches
1 conflict
0x7e1c758b…2f47
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 0xf3fbc9b8fe…77ab58
Audit this contract →
← previous block·next block →recent activity