← previous blocknext block →recent activity

Analyzing

Block #100,726,960

24 transactions · 22 stateful · 2026-08-31 10:02:20 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

0.88

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,726,960  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0xd5bec32a…b8c3

0x34b655…2a6f

6 touches
3 conflicts

0xd97b0449…00a0

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xf6ccd9d6…8754

0x34b655…2a6f

6 touches
3 conflicts

0xd048d318…4d44

0xd32edf…ff58

5 touches
3 conflicts

0x107b89e4…470d

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

10 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity