← previous blocknext block →recent activity

Analyzing

Block #90,808,923

16 transactions · 16 stateful · 2026-07-27 15:35:41 UTC

Parallelism

50/100

Blocked

63%

Avg conflicts / tx

1.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #90,808,923  ·  16 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x4c188934…158e

0x34b655…2a6f

6 touches
3 conflicts

0x58d6b9cf…7c9e

0x34b655…2a6f

6 touches
3 conflicts

0x66e4850e…b021

0x34b655…2a6f

6 touches
3 conflicts

0x69ee34d1…30f8

0x34b655…2a6f

6 touches
3 conflicts

0x6f132c01…cdcc

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity