← previous blocknext block →recent activity

Analyzing

Block #91,136,306

23 transactions · 21 stateful · 2026-07-28 19:03:40 UTC

Parallelism

65/100

Blocked

43%

Avg conflicts / tx

1.35

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #91,136,306  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x3b9bb58c…e73a

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xc0eb79d1…29a4

0x34b655…2a6f

6 touches
3 conflicts

0x98b8e5ef…bda4

0x34b655…2a6f

6 touches
3 conflicts

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0xb56f0740…7542

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity