← previous blocknext block →recent activity
Analyzing
Block #85,160,893
20 transactions · 17 stateful · 2026-07-02 17:54:02 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,160,893 · 20 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
1w02w14w05w06w17w28w312w016w117w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x7fffd49d…772a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdeddb1c8…0d40
0x34b655…2a6f
6 touches
3 conflicts
0x83dee4ed…fbad
0x34b655…2a6f
4 touches
1 conflict
0x94e7f277…471b
0x34b655…2a6f
4 touches
1 conflict
0xafa74bf1…a7d1
0x34b655…2a6f
4 touches
1 conflict
0xc0a4133e…6110
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity