← previous blocknext block →recent activity

Analyzing

Block #98,928,940

27 transactions · 25 stateful · 2026-08-25 02:49:07 UTC

Parallelism

81/100

Blocked

28%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,928,940  ·  27 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x10abefc9…c9bc

0x2b46c0…1669

2 touches
0 conflicts

0x10d80fee…dbda

0x2b46c0…1669

2 touches
0 conflicts

0x40970e69…da50

0x2b46c0…1669

2 touches
0 conflicts

0x8cf3d245…1d0d

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)

10 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity