← previous blocknext block →recent activity
Analyzing
Block #85,129,167
23 transactions · 21 stateful · 2026-07-02 14:22:35 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,129,167 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w09w010w112w115w116w317w421w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b353877…605d
0x34b655…2a6f
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x70b220a8…bd5e
0x34b655…2a6f
4 touches
1 conflict
0x9966da31…0d0f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x5b353877fb…57605d
Audit this contract →
← previous block·next block →recent activity