← previous blocknext block →recent activity

Analyzing

Block #100,139,588

21 transactions · 20 stateful · 2026-08-29 08:43:15 UTC

Parallelism

71/100

Blocked

45%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,139,588  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6426

0x34b655…2a6f

8 touches
6 conflicts

0x1d7bbd81…7cc6

0x34b655…2a6f

8 touches
6 conflicts

0x50c61506…343f

0x34b655…2a6f

6 touches
3 conflicts

0x38bcfe5f…6c71

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

6 touches
3 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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity