← previous blocknext block →recent activity

Analyzing

Block #98,939,660

13 transactions · 13 stateful · 2026-08-25 03:43:02 UTC

Parallelism

85/100

Blocked

31%

Avg conflicts / tx

0.38

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,939,660  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x5f761bb5…b2f6

0x34b655…2a6f

4 touches
1 conflict

0x737a7e44…d8f7

0x34b655…2a6f

4 touches
1 conflict

0x8b780b26…f5ff

0x34b655…2a6f

4 touches
1 conflict

0x98f94c6e…7d0b

0x34b655…2a6f

4 touches
1 conflict

0xbd7e5778…8896

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xdb11940a…519b

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)

1 conflict on slot 0xd17580f913…78ece1

← previous block·next block →recent activity