← previous blocknext block →recent activity

Analyzing

Block #100,984,401

23 transactions · 20 stateful · 2026-09-01 07:37:44 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,984,401  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe98be4ff…d0a2

0x34b655…2a6f

8 touches
6 conflicts

0x898d9b8a…d1ef

0x34b655…2a6f

6 touches
3 conflicts

0xf2880574…4e73

0x34b655…2a6f

6 touches
3 conflicts

0xd7443f37…eb79

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

4 touches
1 conflict

0x953517cb…cdec

0x34b655…2a6f

4 touches
1 conflict

0x9c6a9da2…c628

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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

6 conflicts on slot 0xe98be4ff77…d4d0a2

← previous block·next block →recent activity