← previous blocknext block →recent activity
Analyzing
Block #85,027,632
16 transactions · 13 stateful · 2026-07-02 03:03:27 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,027,632 · 16 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
4w06w19w212w213w314w415w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77dc4958…659e
0x34b655…2a6f
8 touches
6 conflicts
0x117df2e4…ca73
0x34b655…2a6f
6 touches
3 conflicts
0x579ff4a7…6835
0x34b655…2a6f
6 touches
3 conflicts
0x601b810a…1b2b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1c7763f6…89be
0x34b655…2a6f
4 touches
1 conflict
0x49037046…6742
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x77dc495815…97659e
Audit this contract →
← previous block·next block →recent activity