← previous blocknext block →recent activity

Analyzing

Block #91,111,265

19 transactions · 13 stateful · 2026-07-28 16:57:42 UTC

Parallelism

89/100

Blocked

23%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,111,265  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8bddb6c6…c7b0

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x21898044…a071

0x065c9d…c394

4 touches
1 conflict

0xfe53bc30…5d18

0x34b655…2a6f

4 touches
1 conflict

0x9a73834c…0f52

0x34b655…2a6f

4 touches
1 conflict

0x9a73834c…0f51

0x34b655…2a6f

4 touches
1 conflict

0x0d2e1791…c1dd

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

1 conflict on slot 0x737acb7813…fafce8

← previous block·next block →recent activity