← previous blocknext block →recent activity

Analyzing

Block #101,315,636

26 transactions · 21 stateful · 2026-09-02 11:24:32 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,315,636  ·  26 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

0x6a9e408e…3721

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

2 touches
0 conflicts

0xa605468c…1bfc

0x34ae4d…3fc5

2 touches
0 conflicts

0x44b9b01e…d1ce

0x34b655…2a6f

2 touches
0 conflicts

0x4f858307…7642

0x34b655…2a6f

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