← previous blocknext block →recent activity
Analyzing
Block #85,160,545
18 transactions · 17 stateful · 2026-07-02 17:51:44 UTC
Parallelism
78/100
Blocked
59%
Avg conflicts / tx
1.17
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,160,545 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w39w111w012w113w214w316w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4384dd01…4f99
0x34b655…2a6f
8 touches
6 conflicts
0x40b5f387…a164
0x34b655…2a6f
8 touches
6 conflicts
0x42041fec…bd86
0x754704…b603
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x548145a9…cfce
0x34b655…2a6f
6 touches
3 conflicts
0x63b15849…80b2
0x34b655…2a6f
6 touches
3 conflicts
0x87900112…d9ff
0x34b655…2a6f
6 touches
3 conflicts
0x92f12f1d…f71b
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 0x4384dd01db…564f99
Audit this contract →
← previous block·next block →recent activity