← previous blocknext block →recent activity
Analyzing
Block #99,958,152
30 transactions · 29 stateful · 2026-08-28 17:29:35 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
1.13
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,958,152 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w08w29w310w311w415w516w517w620w122w723w128w729w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6d40b7f…2969
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x758a0dd5…0f46
0x34b655…2a6f
6 touches
3 conflicts
0x2288c7e7…982a
0x34b655…2a6f
6 touches
3 conflicts
0x485d2778…aa5c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
15 conflicts on slot 0xa6d40b7f0d…ff2969
Audit this contract →
← previous block·next block →recent activity