← previous blocknext block →recent activity

Analyzing

Block #91,419,090

27 transactions · 25 stateful · 2026-07-29 18:47:41 UTC

Parallelism

63/100

Blocked

56%

Avg conflicts / tx

1.41

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #91,419,090  ·  27 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xfed09e59…a493

0x34b655…2a6f

8 touches
6 conflicts

0xb9834665…e363

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…004c

0x80c745…7210

6 touches
3 conflicts

0x1a7adb59…a2c8

0x34b655…2a6f

6 touches
3 conflicts

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity