← previous blocknext block →recent activity
Analyzing
Block #99,252,936
22 transactions · 18 stateful · 2026-08-26 06:05:54 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,252,936 · 22 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
1w06w07w18w212w014w115w117w218w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x8b98c194…d69e
0x851145…3f07
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x76622fb2…4f08
0x34b655…2a6f
4 touches
1 conflict
0xa2f82062…b4e7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity