← previous blocknext block →recent activity
Analyzing
Block #94,472,709
18 transactions · 18 stateful · 2026-08-09 11:05:20 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.22
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,472,709 · 18 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
2w03w14w25w37w48w511w012w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x38ab7810…35be
0x065c9d…c394
7 touches
6 conflicts
0x74f95963…01a2
0x34b655…2a6f
6 touches
3 conflicts
0x7b987499…a00c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x95c47f03…f1bb
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity