← previous blocknext block →recent activity
Analyzing
Block #99,265,210
29 transactions · 21 stateful · 2026-08-26 07:07:45 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,265,210 · 29 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
1w02w13w04w25w36w07w18w218w319w320w021w122w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x705ab4ae…0162
0x34b655…2a6f
5 touches
3 conflicts
0x30132aa8…4a43
0x34b655…2a6f
5 touches
3 conflicts
0x9db33dcd…202b
0x065c9d…c394
5 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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity