← previous blocknext block →recent activity

Analyzing

Block #100,083,969

24 transactions · 22 stateful · 2026-08-29 04:03:04 UTC

Parallelism

92/100

Blocked

18%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,083,969  ·  24 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x38bcfe5f…6c71

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xec7d120d…7084

0x34b655…2a6f

4 touches
1 conflict

0xedee7e09…6888

0x34b655…2a6f

4 touches
1 conflict

0xfb14d7f1…e509

0x34b655…2a6f

4 touches
1 conflict

0x1f01b15f…a050

0x34b655…2a6f

4 touches
1 conflict

0x69ee34d1…30f8

0x34b655…2a6f

4 touches
1 conflict

0x1408e7c7…f324

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x38bcfe5f82…986c71

← previous block·next block →recent activity