← previous blocknext block →recent activity

Analyzing

Block #97,853,487

17 transactions · 17 stateful · 2026-08-21 07:50:07 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

1.06

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,853,487  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0xdb1e37cb…90c9

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x0e3f9c0d…8a5f

0x34b655…2a6f

2 touches
0 conflicts

0x1cdfe548…d3aa

0x34b655…2a6f

2 touches
0 conflicts

0x213b816c…a5e0

0x34b655…2a6f

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