← previous blocknext block →recent activity

Analyzing

Block #91,086,671

19 transactions · 17 stateful · 2026-07-28 14:53:57 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,086,671  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x703b861a…cbe3

0x188d58…ea8e

4 touches
1 conflict

0x703b861a…cbe5

0x188d58…ea8e

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x03fe94de…ffc8

0x34b655…2a6f

4 touches
1 conflict

0x17885aa8…d92e

0x34b655…2a6f

4 touches
1 conflict

0x1e3dc02f…b1ba

0x34b655…2a6f

4 touches
1 conflict

0x2aab0897…78f7

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity