← previous blocknext block →recent activity

Analyzing

Block #92,174,738

13 transactions · 12 stateful · 2026-08-01 10:09:46 UTC

Parallelism

77/100

Blocked

25%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,174,738  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xe1f61186…e2f8

0x754704…b603

4 touches
1 conflict

0x00000000…0006

0x7b9256…1fb2

4 touches
1 conflict

0x470b2b8d…9545

0x7b9256…1fb2

4 touches
1 conflict

0x470b2b8d…9546

0x7b9256…1fb2

4 touches
1 conflict

0x470b2b8d…9549

0x7b9256…1fb2

4 touches
1 conflict

0x7aacdfba…74c7

0x7b9256…1fb2

4 touches
1 conflict

0x7aacdfba…74c8

0x7b9256…1fb2

4 touches
1 conflict

0x7aacdfba…74c9

0x7b9256…1fb2

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 0xe1f61186c5…67e2f8

← previous block·next block →recent activity