← previous blocknext block →recent activity

Analyzing

Block #91,138,707

17 transactions · 14 stateful · 2026-07-28 19:15:44 UTC

Parallelism

65/100

Blocked

57%

Avg conflicts / tx

1.12

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,138,707  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x737acb78…fce8

0x34b655…2a6f

12 touches
15 conflicts

0xce06a0f7…efef

0x34b655…2a6f

12 touches
15 conflicts

0xbde524f4…43bf

0x34b655…2a6f

12 touches
15 conflicts

0x481b6dfe…ab8e

0x34b655…2a6f

8 touches
6 conflicts

0x513b12c7…47cd

0x34b655…2a6f

7 touches
6 conflicts

0xbc66586e…20fe

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

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

15 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity