← previous blocknext block →recent activity
Analyzing
Block #99,203,168
25 transactions · 23 stateful · 2026-08-26 01:55:31 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,203,168 · 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
6w07w112w215w121w024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x1db5837f…1264
0x34b655…2a6f
4 touches
1 conflict
0x659933ab…e189
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe188ad90…d23f
0x34b655…2a6f
4 touches
1 conflict
0x8fa7a69c…8fd7
0x5ee258…7777
2 touches
0 conflicts
0xb3f28385…15a5
0x5ee258…7777
2 touches
0 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
3 conflicts on slot 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity