← previous blocknext block →recent activity
Analyzing
Block #99,589,548
24 transactions · 22 stateful · 2026-08-27 10:23:32 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.92
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,589,548 · 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
1w02w13w28w29w310w211w415w516w618w723w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10537d06…4472
0x34b655…2a6f
10 touches
10 conflicts
0xfb682e7d…dde9
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xec85b41e…7c92
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0x10537d06a5…4e4472
Audit this contract →
← previous block·next block →recent activity