← previous blocknext block →recent activity

Analyzing

Block #91,438,247

22 transactions · 21 stateful · 2026-07-29 20:24:57 UTC

Parallelism

55/100

Blocked

48%

Avg conflicts / tx

1.27

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #91,438,247  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xd6289e73…4276

0x34b655…2a6f

10 touches
10 conflicts

0x0ab54c30…b88e

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xec530be9…587b

0x34b655…2a6f

6 touches
3 conflicts

0x543e16f7…48ac

0x34b655…2a6f

6 touches
3 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity