← previous blocknext block →recent activity

Analyzing

Block #98,851,895

24 transactions · 21 stateful · 2026-08-24 20:21:31 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,851,895  ·  24 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

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x11b69a7e…334e

0x01bff4…1071

8 touches
6 conflicts

0x7de57974…f5ba

0x34b655…2a6f

6 touches
3 conflicts

0x74831f47…d30b

0x851145…3f07

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x82f46d1e…1831

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity