← previous blocknext block →recent activity

Analyzing

Block #91,417,196

35 transactions · 31 stateful · 2026-07-29 18:38:09 UTC

Parallelism

69/100

Blocked

65%

Avg conflicts / tx

2.09

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #91,417,196  ·  35 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

18 touches
36 conflicts

0x00000000…0002

0x48cba2…b48b

14 touches
21 conflicts

0xefcdf197…96a2

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x20fbcaee…bb79

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x4a5956ef…e226

0x34b655…2a6f

6 touches
3 conflicts

0xc799e56d…45aa

0x34b655…2a6f

4 touches
1 conflict

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

36 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity