← previous blocknext block →recent activity

Analyzing

Block #91,408,740

27 transactions · 24 stateful · 2026-07-29 17:55:30 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

1.41

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #91,408,740  ·  27 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

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xfb874a6c…caa0

0x34b655…2a6f

8 touches
6 conflicts

0x418f6232…2de6

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…004c

0x80c745…7210

6 touches
3 conflicts

0x0e727535…1759

0x34b655…2a6f

6 touches
3 conflicts

0x438f088c…80b1

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity