← previous blocknext block →recent activity
Analyzing
Block #85,195,441
17 transactions · 16 stateful · 2026-07-02 21:44:08 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,195,441 · 17 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
5w07w18w111w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd63e616b…a07d
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf98f45fd…37b1
0x34b655…2a6f
4 touches
1 conflict
0x680f3229…4e58
0x34b655…2a6f
4 touches
1 conflict
0x7585925a…3f45
0x34b655…2a6f
4 touches
1 conflict
0x7f93f2f0…6666
0x34b655…2a6f
4 touches
1 conflict
0x8c41df26…e889
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 0xd63e616b67…7fa07d
Audit this contract →
← previous block·next block →recent activity