← previous blocknext block →recent activity
Analyzing
Block #99,194,611
18 transactions · 18 stateful · 2026-08-26 01:12:28 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,194,611 · 18 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
1w02w13w26w37w08w310w412w013w114w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde0d510e…4037
0x34b655…2a6f
6 touches
3 conflicts
0x41c56387…a8f6
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x93afca4c…b47a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x22e0cc1d…ad0d
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
3 conflicts on slot 0xde0d510e00…a44037
Audit this contract →
← previous block·next block →recent activity