← previous blocknext block →recent activity

Analyzing

Block #120,748,907

23 transactions · 22 stateful · 2026-11-09 12:21:33 UTC

Parallelism

87/100

Blocked

27%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #120,748,907  ·  23 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

0xc2575a0e…f90b

0xf3fb2e…41eb

6 touches
3 conflicts

0x59e4ffbf…f01b

0x34b655…2a6f

6 touches
3 conflicts

0xc2575a0e…f805

0xf3fb2e…41eb

6 touches
3 conflicts

0x2f586c92…e3e1

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6ba2f1d7…cf9d

0x34b655…2a6f

4 touches
1 conflict

0xadae4aae…cc15

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