← previous blocknext block →recent activity

Analyzing

Block #91,109,915

31 transactions · 24 stateful · 2026-07-28 16:50:55 UTC

Parallelism

81/100

Blocked

46%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,109,915  ·  31 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

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x2d93aa7c…07b9

0x34b655…2a6f

10 touches
10 conflicts

0x7be3246e…f89f

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x217bd767…b79e

0x34b655…2a6f

6 touches
3 conflicts

0x685e7bfd…8856

0x34b655…2a6f

6 touches
3 conflicts

0x7dfe7788…8d9f

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 0x482471adbb…39122f

← previous block·next block →recent activity