← previous blocknext block →recent activity

Analyzing

Block #100,978,400

25 transactions · 22 stateful · 2026-09-01 07:07:33 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.64

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #100,978,400  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x26253352…1a75

0x34b655…2a6f

4 touches
1 conflict

0x9a100e05…c541

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x1d9154e7…8821

0x34b655…2a6f

2 touches
0 conflicts

0x25191452…d2ed

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)

36 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity