← previous blocknext block →recent activity

Analyzing

Block #91,255,360

14 transactions · 12 stateful · 2026-07-29 05:02:39 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,255,360  ·  14 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

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xb1b58b33…874f

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x0f8965bb…e238

0x34b655…2a6f

4 touches
1 conflict

0x5d7e0e69…e6d1

0x34b655…2a6f

4 touches
1 conflict

0x5d7e0e69…e6d2

0x34b655…2a6f

4 touches
1 conflict

0x72c8aeb2…9921

0x34b655…2a6f

4 touches
1 conflict

0xd3406c63…f416

0x851145…3f07

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 0x737acb7813…fafce8

← previous block·next block →recent activity