← previous blocknext block →recent activity

Analyzing

Block #91,267,042

23 transactions · 23 stateful · 2026-07-29 06:01:27 UTC

Parallelism

52/100

Blocked

52%

Avg conflicts / tx

1.96

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #91,267,042  ·  23 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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xd66696e0…0842

0x34b655…2a6f

12 touches
15 conflicts

0xf3d10975…0d07

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

12 touches
15 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

12 touches
15 conflicts

0x1fa581e1…53d8

0x34b655…2a6f

10 touches
10 conflicts

0x94de4d05…ad01

0x34b655…2a6f

8 touches
6 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 0xc824469a90…af6425

← previous block·next block →recent activity