← previous blocknext block →recent activity

Analyzing

Block #100,792,030

28 transactions · 21 stateful · 2026-08-31 15:29:51 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.46

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,792,030  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x11b69a7e…334e

0x01bff4…1071

10 touches
10 conflicts

0x07b86c51…cdae

0x2a68ba…90c5

4 touches
1 conflict

0x33c75caf…854c

0x851145…3f07

4 touches
1 conflict

0xfad6ea9e…1fa1

0x851145…3f07

4 touches
1 conflict

0x4213f1c0…219a

0x2a68ba…90c5

4 touches
1 conflict

0x191e0467…70e5

0x34b655…2a6f

4 touches
1 conflict

0x502b3ee1…7f7c

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)

10 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity