← previous blocknext block →recent activity

Analyzing

Block #91,386,263

22 transactions · 20 stateful · 2026-07-29 16:02:10 UTC

Parallelism

45/100

Blocked

75%

Avg conflicts / tx

2.36

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #91,386,263  ·  22 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

16 touches
28 conflicts

0x0ab54c30…b88e

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0x6e6b8ec7…2197

0x34b655…2a6f

6 touches
3 conflicts

0x6ef08b1e…eab6

0x34b655…2a6f

6 touches
3 conflicts

0x73c70c38…41a3

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity