← previous blocknext block →recent activity

Analyzing

Block #100,751,923

26 transactions · 21 stateful · 2026-08-31 12:07:54 UTC

Parallelism

73/100

Blocked

33%

Avg conflicts / tx

0.69

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,751,923  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x23253ea8…e0a4

0x34b655…2a6f

4 touches
1 conflict

0x2d11f5b2…8cb7

0x34b655…2a6f

4 touches
1 conflict

0x31c88cf2…107f

0x34b655…2a6f

4 touches
1 conflict

0x3243e72f…1f6d

0x34b655…2a6f

4 touches
1 conflict

0x36a76bd2…1fb0

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity