← previous blocknext block →recent activity
Analyzing
Block #99,493,117
28 transactions · 24 stateful · 2026-08-27 02:15:05 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,493,117 · 28 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
6w07w18w09w210w011w112w215w116w317w418w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c94fef9…a17f
0x34b655…2a6f
10 touches
10 conflicts
0xfc5356d8…a906
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xac0b4a08…faae
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x931975c2…b7b3
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
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 0x9c94fef939…a0a17f
Audit this contract →
← previous block·next block →recent activity