← previous blocknext block →recent activity

Analyzing

Block #100,616,184

21 transactions · 18 stateful · 2026-08-31 00:45:06 UTC

Parallelism

76/100

Blocked

44%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,616,184  ·  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

0x00000000…003d

0x851145…3f07

6 touches
3 conflicts

0x31762a87…3704

0x851145…3f07

6 touches
3 conflicts

0xf52df78b…16a0

0x851145…3f07

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x7a12283f…b18a

0x2b46c0…1669

4 touches
1 conflict

0x8b2c44b4…7e59

0x2b46c0…1669

4 touches
1 conflict

0x915c095e…c1e5

0x2b46c0…1669

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