← previous blocknext block →recent activity

Analyzing

Block #91,098,910

19 transactions · 16 stateful · 2026-07-28 15:55:33 UTC

Parallelism

84/100

Blocked

44%

Avg conflicts / tx

0.63

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,098,910  ·  19 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

0x1bf8d2af…d140

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x09f6bcb7…e9df

0x34b655…2a6f

4 touches
1 conflict

0x2aab0897…78f7

0x34b655…2a6f

4 touches
1 conflict

0x3b9bb58c…e73a

0x34b655…2a6f

4 touches
1 conflict

0x3bdd71a2…b6eb

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0x1bf8d2afa1…d2d140

← previous block·next block →recent activity