← previous blocknext block →recent activity
Analyzing
Block #99,353,399
22 transactions · 18 stateful · 2026-08-26 14:31:24 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,353,399 · 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
4w05w18w09w110w212w014w116w017w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa0c5188…06f2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x4756e0d1…9aba
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6ac381e3…e686
0x34b655…2a6f
4 touches
1 conflict
0x849a4da4…f503
0x34b655…2a6f
4 touches
1 conflict
0xaba6578d…bd48
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0xfa0c518825…0b06f2
Audit this contract →
← previous block·next block →recent activity