← previous blocknext block →recent activity

Analyzing

Block #101,311,636

21 transactions · 18 stateful · 2026-09-02 11:04:25 UTC

Parallelism

76/100

Blocked

39%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,311,636  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x1a88adfd…93be

0x34b655…2a6f

6 touches
3 conflicts

0x60c15d9f…0643

0x34b655…2a6f

4 touches
1 conflict

0x43e3decb…be40

0x34b655…2a6f

4 touches
1 conflict

0x05732507…d5bf

0x34b655…2a6f

4 touches
1 conflict

0x7c51d9aa…af39

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x68faa0b9…14af

0x98dc6e…8633

2 touches
0 conflicts

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)

10 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity