← previous blocknext block →recent activity
Analyzing
Block #94,229,732
38 transactions · 34 stateful · 2026-08-08 14:31:41 UTC
Parallelism
55/100
Blocked
59%
Avg conflicts / tx
3
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #94,229,732 · 38 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w09w415w416w517w619w721w822w923w1024w1125w1235w1537w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
18 touches
36 conflicts
0xbb322930…ace5
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x6215d3fd…db97
0x34b655…2a6f
14 touches
21 conflicts
0x9d05c3a2…7e0e
0x34b655…2a6f
12 touches
15 conflicts
0xfc3d5171…8357
0x34b655…2a6f
12 touches
15 conflicts
0x48e3acd8…cf41
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity