← previous blocknext block →recent activity
Analyzing
Block #99,360,091
27 transactions · 25 stateful · 2026-08-26 15:05:11 UTC
Parallelism
85/100
Blocked
28%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,360,091 · 27 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
1w03w07w08w19w210w012w115w117w218w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8675c5dc…6f28
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x1d10f24a…2fb8
0xa6afd3…d132
4 touches
1 conflict
0x61571888…b392
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0xd6113c0f…0a4b
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 0x8675c5dc5f…aa6f28
Audit this contract →
← previous block·next block →recent activity