← previous blocknext block →recent activity

Analyzing

Block #100,924,241

22 transactions · 20 stateful · 2026-09-01 02:35:07 UTC

Parallelism

77/100

Blocked

30%

Avg conflicts / tx

0.41

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,924,241  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x382434ca…96b5

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x89999c15…fdac

0x34b655…2a6f

6 touches
3 conflicts

0x2d071de0…c86e

0x34b655…2a6f

4 touches
1 conflict

0x36557a79…cf09

0x34b655…2a6f

4 touches
1 conflict

0x55192654…91fe

0x34b655…2a6f

4 touches
1 conflict

0x5666db7d…5dc4

0x34b655…2a6f

4 touches
1 conflict

0x65e6e603…cb44

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

3 conflicts on slot 0x382434ca57…4d96b5

← previous block·next block →recent activity