← previous blocknext block →recent activity

Analyzing

Block #99,859,496

19 transactions · 18 stateful · 2026-08-28 09:12:26 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,859,496  ·  19 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd17580f9…ece1

0x754704…b603

12 touches
15 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xf2dc7074…4491

0x34b655…2a6f

4 touches
1 conflict

0xfaf5fe80…1ffc

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x24b1c3e2…ff5a

0x34b655…2a6f

2 touches
0 conflicts

0x00532bf5…5711

0x754704…b603

2 touches
0 conflicts

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)

15 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity