← previous blocknext block →recent activity
Analyzing
Block #99,708,458
16 transactions · 15 stateful · 2026-08-27 20:27:40 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,708,458 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w210w211w313w315w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd56bf871…6dae
0x34b655…2a6f
8 touches
6 conflicts
0x08399ab6…0057
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb5bfc097…e790
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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
6 conflicts on slot 0xd56bf871ff…0c6dae
Audit this contract →
← previous block·next block →recent activity