← previous blocknext block →recent activity

Analyzing

Block #101,248,476

13 transactions · 12 stateful · 2026-09-02 05:46:37 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,248,476  ·  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

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0xfa75029c…d62c

0x34b655…2a6f

4 touches
1 conflict

0x2734fe9c…068f

0x34b655…2a6f

4 touches
1 conflict

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0x5814330e…08e9

0x34b655…2a6f

4 touches
1 conflict

0x5b37bb6b…aaff

0x34b655…2a6f

4 touches
1 conflict

0x5b37bb6b…ab00

0x34b655…2a6f

4 touches
1 conflict

0x71ef0b6e…eeaa

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 0xd17580f913…78ece1

← previous block·next block →recent activity