← previous blocknext block →recent activity
Analyzing
Block #94,471,601
30 transactions · 27 stateful · 2026-08-09 10:59:43 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,471,601 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w28w39w010w113w315w418w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74f95963…01a2
0x34b655…2a6f
10 touches
10 conflicts
0xa88a59cd…35ac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5502e1cc…3910
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x9d6946b4…7f4e
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 0x74f9596374…0201a2
Audit this contract →
← previous block·next block →recent activity