← previous blocknext block →recent activity

Analyzing

Block #91,954,446

18 transactions · 15 stateful · 2026-07-31 15:41:49 UTC

Parallelism

83/100

Blocked

20%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,954,446  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbe17f641…9633

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x298e6c6d…6c2a

0x34b655…2a6f

4 touches
1 conflict

0x33649c4f…b327

0x34b655…2a6f

4 touches
1 conflict

0x37da811a…f7dc

0x34b655…2a6f

4 touches
1 conflict

0x58622c15…4dee

0x34b655…2a6f

4 touches
1 conflict

0x6f4e7625…aba5

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0xbe17f64164…b19633

← previous block·next block →recent activity