← previous blocknext block →recent activity

Analyzing

Block #100,733,750

21 transactions · 17 stateful · 2026-08-31 10:36:29 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,733,750  ·  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

0x81716ce9…095f

0x34b655…2a6f

8 touches
6 conflicts

0x68531239…e9a3

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xce519857…e5c4

0x34b655…2a6f

4 touches
1 conflict

0x1408a100…f721

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x6e12568b…9a50

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 0x81716ce924…61095f

← previous block·next block →recent activity