← previous blocknext block →recent activity

Analyzing

Block #91,110,568

24 transactions · 23 stateful · 2026-07-28 16:54:12 UTC

Parallelism

58/100

Blocked

48%

Avg conflicts / tx

1.25

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #91,110,568  ·  24 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x673e2e56…9f5d

0x34b655…2a6f

8 touches
6 conflicts

0x5fab7fbe…1ce5

0x34b655…2a6f

8 touches
6 conflicts

0x217bd767…b79e

0x34b655…2a6f

8 touches
6 conflicts

0x99701186…1cbf

0x34b655…2a6f

8 touches
6 conflicts

0xebb9e0db…9fb4

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

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 0x673e2e5652…b99f5d

← previous block·next block →recent activity