← previous blocknext block →recent activity

Analyzing

Block #98,643,308

19 transactions · 17 stateful · 2026-08-24 02:42:07 UTC

Parallelism

63/100

Blocked

47%

Avg conflicts / tx

1.21

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,643,308  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xa1087a5c…66c4

0x754704…b603

14 touches
21 conflicts

0x11b69a7e…334e

0xee8c0e…1242

14 touches
21 conflicts

0x5971c465…8804

0xa6afd3…d132

6 touches
3 conflicts

0x2a9e9bd1…5368

0x2a68ba…90c5

6 touches
3 conflicts

0xdf496fbf…2e03

0xa6afd3…d132

6 touches
3 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0x5092059d…81ff

0x851145…3f07

4 touches
1 conflict

0x77253a66…396f

0x851145…3f07

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)

21 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity