← previous blocknext block →recent activity
Analyzing
Block #99,092,556
26 transactions · 25 stateful · 2026-08-25 16:38:54 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,092,556 · 26 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
4w05w06w07w08w19w010w114w217w119w120w221w123w224w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d03bddb…6658
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xa6678037…6a10
0x40c49f…2af0
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x0de7749d…5bef
0x34b655…2a6f
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
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 0x0d03bddb26…a56658
Audit this contract →
← previous block·next block →recent activity