← previous blocknext block →recent activity

Analyzing

Block #91,294,295

28 transactions · 21 stateful · 2026-07-29 08:19:19 UTC

Parallelism

75/100

Blocked

43%

Avg conflicts / tx

0.89

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,294,295  ·  28 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xfecb18c0…01ed

0x34b655…2a6f

8 touches
6 conflicts

0x2fd12b6c…02cc

0x34b655…2a6f

8 touches
6 conflicts

0xebac0f82…a49c

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xcc351d6d…256b

0x34b655…2a6f

6 touches
3 conflicts

0x641aed07…bcb9

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

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

6 conflicts on slot 0xfecb18c068…6e01ed

← previous block·next block →recent activity