← previous blocknext block →recent activity

Analyzing

Block #91,159,850

29 transactions · 27 stateful · 2026-07-28 21:02:07 UTC

Parallelism

59/100

Blocked

52%

Avg conflicts / tx

1.62

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #91,159,850  ·  29 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

0x0a0cecef…4ed0

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x00d80c6e…ab3b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x08381baf…6597

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

21 conflicts on slot 0x0a0cecef55…324ed0

← previous block·next block →recent activity