← previous blocknext block →recent activity

Analyzing

Block #99,270,725

23 transactions · 23 stateful · 2026-08-26 07:35:29 UTC

Parallelism

65/100

Blocked

48%

Avg conflicts / tx

1.43

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,270,725  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x08884f7c…c4d0

0x34b655…2a6f

4 touches
1 conflict

0x462c841a…a4c0

0x34b655…2a6f

4 touches
1 conflict

0xa6b48d6e…0705

0x34b655…2a6f

4 touches
1 conflict

0xc3baa205…f26e

0x34b655…2a6f

4 touches
1 conflict

0xe2263bea…6a9d

0x2b46c0…1669

2 touches
0 conflicts

0xe2263bea…6aa2

0x2b46c0…1669

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)

28 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity