← previous blocknext block →recent activity
Analyzing
Block #85,193,324
14 transactions · 13 stateful · 2026-07-02 21:29:57 UTC
Parallelism
43/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,193,324 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1e0175c…5649
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x06aed19e…ca57
0x34b655…2a6f
10 touches
10 conflicts
0xa1571d54…ae41
0x34b655…2a6f
10 touches
10 conflicts
0xd81f9be5…89fb
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x90731a8a…467e
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
10 conflicts on slot 0xf1e0175c33…8c5649
Audit this contract →
← previous block·next block →recent activity