← previous blocknext block →recent activity
Analyzing
Block #85,143,880
25 transactions · 19 stateful · 2026-07-02 16:00:48 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,143,880 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w08w19w210w311w414w015w517w122w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0b9bd73…7f1c
0x34b655…2a6f
8 touches
6 conflicts
0x5b353877…605d
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x264f7d7d…8444
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x06aed19e…ca57
0x34b655…2a6f
6 touches
3 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 conflicts
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 0xc0b9bd73c8…277f1c
Audit this contract →
← previous block·next block →recent activity