← previous blocknext block →recent activity

Analyzing

Block #91,249,268

20 transactions · 19 stateful · 2026-07-29 04:31:58 UTC

Parallelism

40/100

Blocked

63%

Avg conflicts / tx

2.15

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #91,249,268  ·  20 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

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0xbde524f4…43bf

0x34b655…2a6f

12 touches
15 conflicts

0x705ab4ae…0162

0x34b655…2a6f

9 touches
10 conflicts

0xb56f0740…7542

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x6e6b8ec7…2197

0x34b655…2a6f

6 touches
3 conflicts

0xcdb40908…3ccd

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

28 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity