← previous blocknext block →recent activity
Analyzing
Block #85,142,634
21 transactions · 20 stateful · 2026-07-02 15:52:30 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,142,634 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w16w27w314w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2cc62d4…69f6
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xc83310b1…c778
0x34b655…2a6f
8 touches
6 conflicts
0xf2112d98…bb04
0x34b655…2a6f
7 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x04123852…24d5
0x34b655…2a6f
6 touches
3 conflicts
0x6f59855d…4191
0x34b655…2a6f
6 touches
3 conflicts
0x7ae63663…9d94
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 0xa2cc62d47b…cc69f6
Audit this contract →
← previous block·next block →recent activity