← previous blocknext block →recent activity

Analyzing

Block #100,063,493

24 transactions · 24 stateful · 2026-08-29 02:19:59 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.29

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #100,063,493  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xd2a76d80…ee44

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x948836ff…59ab

0x34b655…2a6f

4 touches
2 conflicts

0x6119ad89…63fe

0x34b655…2a6f

4 touches
2 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

21 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity