← previous blocknext block →recent activity
Analyzing
Block #85,518,090
20 transactions · 18 stateful · 2026-07-04 09:32:50 UTC
Parallelism
85/100
Blocked
28%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,518,090 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w210w215w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e4b5149…c444
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb319070b…881f
0x065c9d…c394
5 touches
3 conflicts
0x309ef367…e8a1
0x34b655…2a6f
4 touches
1 conflict
0x3a7091da…f2eb
0x34b655…2a6f
4 touches
1 conflict
0x3ab8d9b2…7c22
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
3 conflicts on slot 0x7e4b51491a…71c444
Audit this contract →
← previous block·next block →recent activity