← previous blocknext block →recent activity

Analyzing

Block #90,852,304

18 transactions · 18 stateful · 2026-07-27 19:13:59 UTC

Parallelism

56/100

Blocked

56%

Avg conflicts / tx

1.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #90,852,304  ·  18 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

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0x11b69a7e…334e

0x01bff4…1071

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x734ee320…caae

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 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

10 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity