← previous blocknext block →recent activity

Analyzing

Block #100,248,574

22 transactions · 21 stateful · 2026-08-29 17:52:33 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,248,574  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x9d6a99f9…da64

0x34b655…2a6f

6 touches
3 conflicts

0x74e485b1…d380

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x366a19b0…f065

0x34b655…2a6f

4 touches
1 conflict

0x451e482b…7e7d

0x34b655…2a6f

4 touches
1 conflict

0x5f251b96…6054

0x34b655…2a6f

4 touches
1 conflict

0x5f46663c…b4c2

0x34b655…2a6f

4 touches
1 conflict

0x68292fe7…d918

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

3 conflicts on slot 0x9d6a99f99b…bfda64

← previous block·next block →recent activity