← previous blocknext block →recent activity

Analyzing

Block #91,210,467

21 transactions · 19 stateful · 2026-07-29 01:16:43 UTC

Parallelism

67/100

Blocked

42%

Avg conflicts / tx

0.86

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,210,467  ·  21 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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0x2916c5cb…b0e5

0x34b655…2a6f

6 touches
3 conflicts

0xefcdf197…96a2

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x1526b11f…8b21

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…642d

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 0xac2a02739b…81721b

← previous block·next block →recent activity