← previous blocknext block →recent activity
Analyzing
Block #99,210,324
23 transactions · 15 stateful · 2026-08-26 02:31:31 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,210,324 · 23 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
1w03w15w29w015w116w218w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xb2d8af24…4750
0x34b655…2a6f
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0xfa7f1016…aa21
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xfa57bde8…9d92
0x34b655…2a6f
4 touches
1 conflict
0x2a4120f4…9a05
0x40c49f…2af0
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity