← previous blocknext block →recent activity
Analyzing
Block #94,752,794
52 transactions · 49 stateful · 2026-08-10 10:35:24 UTC
Parallelism
64/100
Blocked
67%
Avg conflicts / tx
2.5
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #94,752,794 · 52 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w07w18w09w110w211w318w123w334w136w237w1039w1140w1241w1346w247w1548w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0x261cbea7…e35e
0x34b655…2a6f
10 touches
10 conflicts
0x52aa1020…c85c
0x34b655…2a6f
10 touches
10 conflicts
0x261cbea7…e35d
0x34b655…2a6f
10 touches
10 conflicts
0x93b6fab0…09d6
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
28 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity