← previous blocknext block →recent activity

Analyzing

Block #91,410,677

28 transactions · 21 stateful · 2026-07-29 18:05:19 UTC

Parallelism

57/100

Blocked

67%

Avg conflicts / tx

1.5

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #91,410,677  ·  28 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x6fe7d366…78ff

0x34b655…2a6f

14 touches
21 conflicts

0x5fe7e126…6dd2

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xacf2813c…1964

0x34b655…2a6f

6 touches
3 conflicts

0x49e721de…b35a

0x34b655…2a6f

6 touches
3 conflicts

0xbabe821d…939b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2fd12b6c…02cc

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity