← previous blocknext block →recent activity

Analyzing

Block #100,864,291

21 transactions · 17 stateful · 2026-08-31 21:33:35 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,864,291  ·  21 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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0xd895ee0b…d301

0x34b655…2a6f

6 touches
3 conflicts

0x2a6c7002…ba26

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5387419f…92b9

0x34b655…2a6f

4 touches
1 conflict

0x5c455afd…ce06

0x34b655…2a6f

4 touches
1 conflict

0x62910921…3016

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity