← previous blocknext block →recent activity

Analyzing

Block #100,603,695

28 transactions · 24 stateful · 2026-08-30 23:42:16 UTC

Parallelism

75/100

Blocked

58%

Avg conflicts / tx

1.21

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,603,695  ·  28 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

0xca841faa…486a

0x34b655…2a6f

14 touches
21 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x9a8482cc…8bee

0x34b655…2a6f

6 touches
3 conflicts

0xc95f91db…a901

0x34b655…2a6f

6 touches
3 conflicts

0x36918c55…8424

0x34b655…2a6f

4 touches
1 conflict

0x3c069597…f18f

0x34b655…2a6f

4 touches
1 conflict

0x451e482b…7e7d

0x34b655…2a6f

4 touches
1 conflict

0x5b89308d…fa8d

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

21 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity