← previous blocknext block →recent activity
Analyzing
Block #99,366,646
31 transactions · 23 stateful · 2026-08-26 15:38:14 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,366,646 · 31 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
1w03w14w25w06w18w210w111w212w217w019w123w129w030w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3c05624…3417
0x34b655…2a6f
8 touches
6 conflicts
0xccdc32f8…72be
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa3c36de0…3cf3
0x34b655…2a6f
6 touches
3 conflicts
0x27cb7116…540e
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x13c2d063…ad08
0x065c9d…c394
5 touches
3 conflicts
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
6 conflicts on slot 0xd3c0562470…3e3417
Audit this contract →
← previous block·next block →recent activity