← previous blocknext block →recent activity
Analyzing
Block #85,131,648
18 transactions · 15 stateful · 2026-07-02 14:39:11 UTC
Parallelism
61/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,131,648 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w011w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x9495bffc…46e6
0x34b655…2a6f
6 touches
3 conflicts
0x264f7d7d…8444
0x34b655…2a6f
4 touches
1 conflict
0x2b779824…4acc
0x34b655…2a6f
4 touches
1 conflict
0x4bf53c98…ec58
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x5b353877…605d
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity