← previous blocknext block →recent activity
Analyzing
Block #94,306,227
13 transactions · 9 stateful · 2026-08-08 20:59:20 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,306,227 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
4 touches
1 conflict
0xe75060c3…b41e
0x34b655…2a6f
4 touches
1 conflict
0x2c276372…eeac
0xa6afd3…d132
3 touches
1 conflict
0x706c758c…2fdb
0x34b655…2a6f
2 touches
0 conflicts
0x8ce19e5c…e818
0x34b655…2a6f
2 touches
0 conflicts
0xa92fc25f…0349
0x34b655…2a6f
2 touches
0 conflicts
0xaf50fd64…63f3
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity