← previous blocknext block →recent activity

Analyzing

Block #99,157,444

22 transactions · 15 stateful · 2026-08-25 22:05:29 UTC

Parallelism

86/100

Blocked

40%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,157,444  ·  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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x18e86f02…fa98

0x34b655…2a6f

4 touches
1 conflict

0x1c0d0b9b…6891

0x34b655…2a6f

4 touches
1 conflict

0x2ea28e1c…4cde

0x34b655…2a6f

4 touches
1 conflict

0x40c6d6fe…1b35

0x34b655…2a6f

4 touches
1 conflict

0x4786839b…c29a

0x34b655…2a6f

4 touches
1 conflict

0x6183ee9a…21b1

0x34b655…2a6f

4 touches
1 conflict

0x706c758c…2fdb

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: USDC (USDC)

3 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity