← previous blocknext block →recent activity
Analyzing
Block #94,859,772
10 transactions · 10 stateful · 2026-08-10 19:33:42 UTC
Parallelism
30/100
Blocked
70%
Avg conflicts / tx
2.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,859,772 · 10 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x216ffe66…1f94
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0xb688ed23…1cf3
0x34b655…2a6f
8 touches
6 conflicts
0xcc89daf5…504e
0x34b655…2a6f
6 touches
3 conflicts
0xe2b988ac…37d8
0x34b655…2a6f
6 touches
3 conflicts
0xac3e4969…39e9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x216ffe6648…bf1f94
Audit this contract →
← previous block·next block →recent activity