← previous blocknext block →recent activity

Analyzing

Block #100,751,058

21 transactions · 18 stateful · 2026-08-31 12:03:33 UTC

Parallelism

76/100

Blocked

39%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,751,058  ·  21 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x2f0c9444…c01f

0x34b655…2a6f

4 touches
1 conflict

0x36a76bd2…1fb0

0x34b655…2a6f

4 touches
1 conflict

0x68c07cb9…ae14

0x34b655…2a6f

4 touches
1 conflict

0x8b3b8057…58fa

0x34b655…2a6f

4 touches
1 conflict

0x98834cc0…6c23

0x34b655…2a6f

4 touches
1 conflict

0x9b79a099…c6f3

0x34b655…2a6f

4 touches
1 conflict

0xa62ab701…3df2

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: Perpl

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity