← previous blocknext block →recent activity

Analyzing

Block #91,558,591

21 transactions · 19 stateful · 2026-07-30 06:30:24 UTC

Parallelism

52/100

Blocked

53%

Avg conflicts / tx

1.67

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #91,558,591  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xcc58c80b…ff79

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xed59b1cd…8509

0x34b655…2a6f

6 touches
3 conflicts

0x90be031d…01c6

0x34b655…2a6f

6 touches
3 conflicts

0xcda18b0b…6a4c

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity