← previous blocknext block →recent activity

Analyzing

Block #91,254,755

21 transactions · 17 stateful · 2026-07-29 04:59:36 UTC

Parallelism

62/100

Blocked

53%

Avg conflicts / tx

0.9

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #91,254,755  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0x262d5015…771b

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x07d8b1e8…78c6

0x34b655…2a6f

6 touches
3 conflicts

0xcf6ec045…15ed

0x34b655…2a6f

5 touches
3 conflicts

0x44a4d86c…1b5e

0x34b655…2a6f

5 touches
3 conflicts

0x705ab4ae…0162

0x34b655…2a6f

5 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

10 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity