← previous blocknext block →recent activity

Analyzing

Block #98,095,911

33 transactions · 25 stateful · 2026-08-22 04:20:49 UTC

Parallelism

94/100

Blocked

20%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,095,911  ·  33 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

0xd4c946a4…b8d4

0x754704…b603

4 touches
1 conflict

0x45436af6…437f

0x99c7a7…8bf0

4 touches
1 conflict

0x66300207…c47a

0x99c7a7…8bf0

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0xd4c946a466…37b8d4

← previous block·next block →recent activity