← previous blocknext block →recent activity
Analyzing
Block #85,570,499
30 transactions · 20 stateful · 2026-07-04 15:21:50 UTC
Parallelism
87/100
Blocked
40%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,570,499 · 30 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
1w03w14w25w06w07w117w018w119w220w324w127w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4150f34…bfea
0x34b655…2a6f
8 touches
6 conflicts
0xb0446875…2b96
0x34b655…2a6f
8 touches
6 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
8 touches
6 conflicts
0x757b0543…e087
0x34b655…2a6f
6 touches
3 conflicts
0xc65eac30…ef1b
0xd32edf…ff58
5 touches
3 conflicts
0x45597879…8174
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 0xf4150f3475…7cbfea
Audit this contract →
← previous block·next block →recent activity