← previous blocknext block →recent activity

Analyzing

Block #100,811,180

22 transactions · 20 stateful · 2026-08-31 17:06:12 UTC

Parallelism

77/100

Blocked

35%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,811,180  ·  22 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

0x11b69a7e…334e

0x01bff4…1071

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x50b0b6ba…336a

0x851145…3f07

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd814f518…f5b4

0x34b655…2a6f

4 touches
1 conflict

0xd895ee0b…d301

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: 0x01bff417…bc1071

10 conflicts on slot 0x11b69a7ea1…83334e

← previous block·next block →recent activity