← previous blocknext block →recent activity

Analyzing

Block #98,655,812

20 transactions · 20 stateful · 2026-08-24 03:47:20 UTC

Parallelism

65/100

Blocked

40%

Avg conflicts / tx

1.15

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,655,812  ·  20 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

0xd17580f9…ece1

0x754704…b603

14 touches
21 conflicts

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x3ca268be…8865

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x6e041be4…a879

0x34b655…2a6f

4 touches
1 conflict

0xbec23443…9293

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

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 0xd17580f913…78ece1

← previous block·next block →recent activity