← previous blocknext block →recent activity

Analyzing

Block #91,422,740

21 transactions · 19 stateful · 2026-07-29 19:06:02 UTC

Parallelism

76/100

Blocked

37%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,422,740  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc0eb79d1…29a4

0x34b655…2a6f

6 touches
3 conflicts

0x231ccc13…a7c6

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x49fc2bf5…7d91

0x34b655…2a6f

4 touches
1 conflict

0x4b1134d6…20c9

0x34b655…2a6f

4 touches
1 conflict

0x5502e1cc…3910

0x34b655…2a6f

4 touches
1 conflict

0x67bfbc55…7b2f

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

3 conflicts on slot 0xc0eb79d1cb…5529a4

← previous block·next block →recent activity