← previous blocknext block →recent activity

Analyzing

Block #102,861,914

25 transactions · 23 stateful · 2026-09-07 21:34:40 UTC

Parallelism

64/100

Blocked

52%

Avg conflicts / tx

1.72

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #102,861,914  ·  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

8 touches
6 conflicts

0x7dd96c96…7335

0x34b655…2a6f

6 touches
3 conflicts

0xb75367ff…a2b7

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x388f889f…a655

0x34b655…2a6f

4 touches
1 conflict

0x327c57dd…836d

0x34b655…2a6f

4 touches
1 conflict

0x4f2e1481…fa91

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)

36 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity