← previous blocknext block →recent activity

Analyzing

Block #91,075,061

14 transactions · 11 stateful · 2026-07-28 13:55:29 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,075,061  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x25d52624…f992

0x34b655…2a6f

4 touches
1 conflict

0x2a21b53a…211b

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0x6bdb9869…7558

0x34b655…2a6f

4 touches
1 conflict

0x9d9bed71…d466

0x34b655…2a6f

4 touches
1 conflict

0xdbe3f23a…ca17

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity