← previous blocknext block →recent activity

Analyzing

Block #91,161,027

15 transactions · 15 stateful · 2026-07-28 21:08:02 UTC

Parallelism

80/100

Blocked

27%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,161,027  ·  15 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

0xebac0f82…a49c

0x34b655…2a6f

6 touches
3 conflicts

0x2f538e43…17b2

0x34b655…2a6f

4 touches
1 conflict

0x36890fff…f3d1

0x34b655…2a6f

4 touches
1 conflict

0x4f0f32bc…a96f

0x34b655…2a6f

4 touches
1 conflict

0x5878b60b…ea9c

0x34b655…2a6f

4 touches
1 conflict

0x5d832806…eb38

0x34b655…2a6f

4 touches
1 conflict

0x5efd7300…d8a5

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

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 0xebac0f82ec…86a49c

← previous block·next block →recent activity