← previous blocknext block →recent activity

Analyzing

Block #100,143,859

29 transactions · 20 stateful · 2026-08-29 09:04:46 UTC

Parallelism

83/100

Blocked

45%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,143,859  ·  29 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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x948836ff…59ab

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0xf98c943e…7c44

0x34b655…2a6f

8 touches
6 conflicts

0x2d6af7d3…5e30

0x34b655…2a6f

5 touches
3 conflicts

0x5ddba9ad…6622

0x34b655…2a6f

5 touches
3 conflicts

0x664fee5f…554b

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 0x482471adbb…39122f

← previous block·next block →recent activity