← previous blocknext block →recent activity
Analyzing
Block #85,138,075
18 transactions · 17 stateful · 2026-07-02 15:22:04 UTC
Parallelism
72/100
Blocked
59%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,138,075 · 18 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
1w02w13w24w05w16w07w18w29w312w214w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1111a1a…f235
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x5e1fa384…8c08
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x191c9934…f4f4
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x9babae38…7a68
0x34b655…2a6f
6 touches
3 conflicts
0xa0efa7bc…8b24
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
10 conflicts on slot 0xa1111a1a35…b4f235
Audit this contract →
← previous block·next block →recent activity