← previous blocknext block →recent activity

Analyzing

Block #100,747,966

20 transactions · 19 stateful · 2026-08-31 11:48:00 UTC

Parallelism

70/100

Blocked

37%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,747,966  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x25180879…8191

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x5086c64a…28ba

0x34b655…2a6f

6 touches
3 conflicts

0xf9302129…0caa

0x34b655…2a6f

6 touches
3 conflicts

0x3aedb1fd…db38

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x502b3ee1…7f7c

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 0x25180879df…1c8191

← previous block·next block →recent activity