← previous blocknext block →recent activity
Analyzing
Block #99,191,850
29 transactions · 25 stateful · 2026-08-26 00:58:35 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,191,850 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w08w110w211w112w013w114w219w320w121w422w523w225w226w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34bf5f17…1bb1
0x34b655…2a6f
6 touches
3 conflicts
0x436357fe…ee27
0x34b655…2a6f
6 touches
3 conflicts
0x6bce5317…a995
0x34b655…2a6f
6 touches
3 conflicts
0x0f8965bb…e238
0x34b655…2a6f
6 touches
3 conflicts
0xf84cab46…0d6c
0x34b655…2a6f
6 touches
3 conflicts
0xfa09be5a…1e79
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
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 0x34bf5f1727…481bb1
Audit this contract →
← previous block·next block →recent activity