← previous blocknext block →recent activity

Analyzing

Block #98,655,849

27 transactions · 21 stateful · 2026-08-24 03:47:31 UTC

Parallelism

67/100

Blocked

43%

Avg conflicts / tx

1.37

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #98,655,849  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x11258774…9892

0x2a68ba…90c5

2 touches
0 conflicts

0x06e40499…165e

0x2b46c0…1669

2 touches
0 conflicts

0xa605468c…1bfc

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)

36 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity