← previous blocknext block →recent activity
Analyzing
Block #99,491,066
24 transactions · 23 stateful · 2026-08-27 02:04:46 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
1.08
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,491,066 · 24 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
1w07w08w19w210w012w313w414w518w619w720w621w723w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2042b9b…0ecb
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00500a94…20d5
0x34b655…2a6f
6 touches
3 conflicts
0x2aab0897…78f7
0x34b655…2a6f
6 touches
3 conflicts
0xdc8d7edd…8a03
0x34b655…2a6f
6 touches
3 conflicts
0xfc8d572c…b27d
0x34b655…2a6f
6 touches
3 conflicts
0x5c455afd…ce06
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
10 conflicts on slot 0xa2042b9b04…e00ecb
Audit this contract →
← previous block·next block →recent activity