← previous blocknext block →recent activity

Analyzing

Block #100,786,755

20 transactions · 17 stateful · 2026-08-31 15:03:17 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,786,755  ·  20 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

0x79347b24…9fba

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x1d351a9b…f2dd

0x34b655…2a6f

4 touches
1 conflict

0x3e2691ca…da1c

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4b57a366…3c96

0x34b655…2a6f

4 touches
1 conflict

0x7462b8f2…6312

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 0x79347b2491…eb9fba

← previous block·next block →recent activity