← previous blocknext block →recent activity

Analyzing

Block #100,439,220

19 transactions · 18 stateful · 2026-08-30 09:54:47 UTC

Parallelism

58/100

Blocked

50%

Avg conflicts / tx

1.58

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #100,439,220  ·  19 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

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x3a37aad1…720f

0x34b655…2a6f

4 touches
1 conflict

0x6063145b…03ae

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xf63c2a2b…bc5f

0x34b655…2a6f

4 touches
1 conflict

0xf63c2a2b…bc60

0x34b655…2a6f

4 touches
1 conflict

0x70e677f5…e3bd

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)

28 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity