← previous blocknext block →recent activity

Analyzing

Block #102,871,528

23 transactions · 21 stateful · 2026-09-07 22:23:03 UTC

Parallelism

65/100

Blocked

43%

Avg conflicts / tx

1.35

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,871,528  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x21e79ad8…c5db

0x34b655…2a6f

2 touches
0 conflicts

0x229d2b7e…abdf

0x34b655…2a6f

2 touches
0 conflicts

0x22badbc6…4c24

0x34b655…2a6f

2 touches
0 conflicts

0x2f50c84a…3640

0x34b655…2a6f

2 touches
0 conflicts

0x3243e72f…1f6d

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)

28 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity