← previous blocknext block →recent activity

Analyzing

Block #100,063,715

23 transactions · 21 stateful · 2026-08-29 02:21:06 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.91

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,063,715  ·  23 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

0xf98c943e…7c44

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xe1681c4c…5858

0x34b655…2a6f

6 touches
3 conflicts

0xeb679f31…8fc1

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0xfaf89f45…ced6

0x34b655…2a6f

6 touches
3 conflicts

0x8dad7932…7029

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 0xf98c943e1d…327c44

← previous block·next block →recent activity