← previous blocknext block →recent activity

Analyzing

Block #100,080,532

20 transactions · 19 stateful · 2026-08-29 03:45:46 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,080,532  ·  20 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

0x97559ec1…f88c

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xa11b60f7…8e8b

0x34b655…2a6f

8 touches
6 conflicts

0x82dbd1ce…c027

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x9cf9008a…d826

0x34b655…2a6f

4 touches
1 conflict

0xbf3b12e0…35d9

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641d

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 0x97559ec1df…51f88c

← previous block·next block →recent activity