← previous blocknext block →recent activity
Analyzing
Block #99,203,318
42 transactions · 36 stateful · 2026-08-26 01:56:16 UTC
Parallelism
69/100
Blocked
69%
Avg conflicts / tx
2.12
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #99,203,318 · 42 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w17w18w19w210w311w414w515w617w219w220w222w323w424w529w634w636w737w839w1040w1141w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x9a100e05…c541
0x34b655…2a6f
10 touches
10 conflicts
0xd1480c90…ae06
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity