← previous blocknext block →recent activity

Analyzing

Block #101,324,314

20 transactions · 19 stateful · 2026-09-02 12:08:12 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,324,314  ·  20 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

0x2a07e64e…fe77

0x754704…b603

6 touches
3 conflicts

0x00000000…0008

0x8964d7…10f8

6 touches
3 conflicts

0x357b8e20…a82f

0x8964d7…10f8

4 touches
1 conflict

0x357b8e20…a832

0x8964d7…10f8

4 touches
1 conflict

0x357b8e20…a833

0x8964d7…10f8

4 touches
1 conflict

0xbb975a6c…bff4

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x140aba89…d7ae

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)

3 conflicts on slot 0x2a07e64ef2…a8fe77

← previous block·next block →recent activity