← previous blocknext block →recent activity

Analyzing

Block #97,197,526

11 transactions · 9 stateful · 2026-08-19 00:01:24 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.27

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #97,197,526  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x8329c51e…4064

0x34b655…2a6f

4 touches
1 conflict

0x8329c51e…4065

0x34b655…2a6f

4 touches
1 conflict

0x9711d99c…3d4c

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xcd93b2d2…30e6

0x34b655…2a6f

4 touches
1 conflict

0xe6bbe9d6…66f0

0x34b655…2a6f

4 touches
1 conflict

0xe9662735…4f99

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)

1 conflict on slot 0xd17580f913…78ece1

← previous block·next block →recent activity