← previous blocknext block →recent activity

Analyzing

Block #90,791,085

17 transactions · 16 stateful · 2026-07-27 14:05:56 UTC

Parallelism

47/100

Blocked

63%

Avg conflicts / tx

1.59

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #90,791,085  ·  17 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

0xbf78ee7f…e7fd

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x5a100ac0…96d3

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x947f1921…b1ba

0x34b655…2a6f

6 touches
3 conflicts

0x9fe82ab3…218f

0x34b655…2a6f

6 touches
3 conflicts

0xa24365bc…5064

0x34b655…2a6f

6 touches
3 conflicts

0xb45aa4f1…693d

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 0xbf78ee7fb5…b5e7fd

← previous block·next block →recent activity