← previous blocknext block →recent activity
Analyzing
Block #99,194,710
20 transactions · 19 stateful · 2026-08-26 01:12:58 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,194,710 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w48w09w111w216w217w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
8 touches
6 conflicts
0x9a100e05…c541
0x34b655…2a6f
6 touches
3 conflicts
0x137247ba…5992
0x34b655…2a6f
6 touches
3 conflicts
0x4757fc7b…70b7
0x34b655…2a6f
6 touches
3 conflicts
0x587cd094…a294
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity