← previous blocknext block →recent activity

Analyzing

Block #100,631,984

20 transactions · 16 stateful · 2026-08-31 02:04:35 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.2

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,631,984  ·  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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xf98c943e…7c44

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xfcea499d…d54d

0x34b655…2a6f

6 touches
3 conflicts

0xa242e227…2e45

0x34b655…2a6f

6 touches
3 conflicts

0x61571888…b392

0x34b655…2a6f

6 touches
3 conflicts

0xafb22303…6db3

0x34b655…2a6f

4 touches
1 conflict

0xb409e204…89ac

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 0xc824469a90…af6425

← previous block·next block →recent activity