← previous blocknext block →recent activity
Analyzing
Block #85,893,309
34 transactions · 19 stateful · 2026-07-06 03:12:46 UTC
Parallelism
85/100
Blocked
37%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,893,309 · 34 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
1w02w13w214w019w126w028w131w232w333w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x08d66073…e706
0x34b655…2a6f
6 touches
3 conflicts
0xc857b971…0bcf
0x34b655…2a6f
5 touches
3 conflicts
0xed59b1cd…8509
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xc6f3c5a3…3faa
0x34b655…2a6f
4 touches
1 conflict
0x7560da7d…a39c
0xa6afd3…d132
3 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity