← previous blocknext block →recent activity

Analyzing

Block #90,820,911

26 transactions · 22 stateful · 2026-07-27 16:36:05 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.58

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,820,911  ·  26 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

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x25e6f91a…a6a4

0x34b655…2a6f

4 touches
1 conflict

0x26d1c221…4d2a

0x34b655…2a6f

4 touches
1 conflict

0x438268c2…c848

0x34b655…2a6f

4 touches
1 conflict

0x438268c2…c849

0x34b655…2a6f

4 touches
1 conflict

0x5e2ea201…12de

0x34b655…2a6f

4 touches
1 conflict

0x67a56c8b…f955

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity