← previous blocknext block →recent activity
Analyzing
Block #85,210,674
34 transactions · 23 stateful · 2026-07-02 23:25:29 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,210,674 · 34 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
1w02w03w04w15w26w317w018w019w120w221w323w025w126w131w132w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44564d6…bb43
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x1ee44d08…7262
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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 0xb44564d6a3…0fbb43
Audit this contract →
← previous block·next block →recent activity