← previous blocknext block →recent activity
Analyzing
Block #85,168,303
23 transactions · 21 stateful · 2026-07-02 18:43:23 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,168,303 · 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
1w03w04w05w16w17w211w315w116w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fffd49d…772a
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x4a5dac02…9503
0x34b655…2a6f
6 touches
3 conflicts
0xd1fe26e6…8d31
0x34b655…2a6f
6 touches
3 conflicts
0x08d66073…e706
0x34b655…2a6f
4 touches
1 conflict
0x0e5f2a94…4732
0x34b655…2a6f
4 touches
1 conflict
0x16b3a441…13db
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
6 conflicts on slot 0x7fffd49db6…f8772a
Audit this contract →
← previous block·next block →recent activity