← previous blocknext block →recent activity

Analyzing

Block #91,387,210

26 transactions · 26 stateful · 2026-07-29 16:06:56 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.19

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #91,387,210  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x07d8b1e8…78c6

0x34b655…2a6f

12 touches
15 conflicts

0x447c249a…b42c

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…004c

0x80c745…7210

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x72083f0d…082a

0x34b655…2a6f

6 touches
3 conflicts

0x9a3068dd…18f0

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

15 conflicts on slot 0x07d8b1e8f0…0978c6

← previous block·next block →recent activity