← previous blocknext block →recent activity

Analyzing

Block #91,250,848

22 transactions · 16 stateful · 2026-07-29 04:39:55 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,250,848  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x28ceceef…ecc2

0x34b655…2a6f

8 touches
6 conflicts

0x91b0f8ed…6bd7

0x34b655…2a6f

6 touches
3 conflicts

0x91b0f8ed…6bd6

0x34b655…2a6f

6 touches
3 conflicts

0x383472f3…bdbc

0x34b655…2a6f

6 touches
3 conflicts

0xda2ee2e7…968a

0x34b655…2a6f

6 touches
3 conflicts

0x805d08cf…3cfc

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

← previous block·next block →recent activity