← previous blocknext block →recent activity

Analyzing

Block #98,090,478

22 transactions · 19 stateful · 2026-08-22 03:53:29 UTC

Parallelism

64/100

Blocked

47%

Avg conflicts / tx

1.36

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #98,090,478  ·  22 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

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xd7443f37…eb79

0x34b655…2a6f

4 touches
1 conflict

0x88661941…8e25

0x34b655…2a6f

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e017

0x188d58…ea8e

2 touches
0 conflicts

0x889d5e90…929a

0x2a68ba…90c5

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