← previous blocknext block →recent activity
Analyzing
Block #85,126,494
23 transactions · 17 stateful · 2026-07-02 14:04:43 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,126,494 · 23 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
1w03w14w05w07w111w012w113w214w316w117w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79b3209b…f766
0x34b655…2a6f
8 touches
6 conflicts
0x63da0619…7a55
0x34b655…2a6f
6 touches
3 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x601a3731…1db5
0x34b655…2a6f
4 touches
1 conflict
0x742072b0…1af8
0x34b655…2a6f
4 touches
1 conflict
0x7523ad90…2ba5
0x34b655…2a6f
4 touches
1 conflict
0x82ee3ad5…ce29
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 0x79b3209b12…57f766
Audit this contract →
← previous block·next block →recent activity