← previous blocknext block →recent activity
Analyzing
Block #99,089,088
25 transactions · 19 stateful · 2026-08-25 16:21:25 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,089,088 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w17w210w011w218w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x470b41f6…fc68
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xde5d4b56…5fa0
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5a6c91e3…7d42
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0xbc5fc032…8d7d
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
3 conflicts on slot 0x470b41f691…2dfc68
Audit this contract →
← previous block·next block →recent activity