← previous blocknext block →recent activity

Analyzing

Block #98,938,983

21 transactions · 20 stateful · 2026-08-25 03:39:38 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,938,983  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x41335ddf…94b9

0x34b655…2a6f

6 touches
3 conflicts

0x4038686e…5e2a

0x34b655…2a6f

4 touches
1 conflict

0x48717abe…be13

0x34b655…2a6f

4 touches
1 conflict

0x5095e01b…5cf0

0x34b655…2a6f

4 touches
1 conflict

0x5aed1bd2…7afa

0x34b655…2a6f

4 touches
1 conflict

0x6c844cea…7bec

0x34b655…2a6f

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)

6 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity