← previous blocknext block →recent activity
Analyzing
Block #94,741,565
51 transactions · 43 stateful · 2026-08-10 09:38:13 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
2.55
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #94,741,565 · 51 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w010w011w112w213w319w521w622w724w826w927w1028w1130w1331w1432w1549w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0xc6b604e6…5152
0x34b655…2a6f
20 touches
45 conflicts
0xc9c603ba…3c4a
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x1d433c71…7370
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
10 touches
10 conflicts
0xe66201d4…84f1
0x34b655…2a6f
8 touches
6 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
55 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity