← previous blocknext block →recent activity

Analyzing

Block #99,284,868

17 transactions · 17 stateful · 2026-08-26 08:46:38 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,284,868  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x066903bd…c1cc

0x77d53b…8080

4 touches
1 conflict

0x066903bd…c1cf

0x77d53b…8080

4 touches
1 conflict

0x066903bd…c1e1

0x77d53b…8080

4 touches
1 conflict

0x0fd2cbc5…476b

0x77d53b…8080

4 touches
1 conflict

0x43a87e36…ae04

0x77d53b…8080

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)

15 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity