← previous blocknext block →recent activity

Analyzing

Block #91,272,792

23 transactions · 22 stateful · 2026-07-29 06:31:03 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1.35

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #91,272,792  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xfed09e59…a493

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x2fd12b6c…02cc

0x34b655…2a6f

8 touches
6 conflicts

0xf4f9cac7…fd98

0x34b655…2a6f

6 touches
3 conflicts

0x231ccc13…a7c6

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xebac0f82…a49c

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 0xfed09e59c7…d6a493

← previous block·next block →recent activity