← previous blocknext block →recent activity

Analyzing

Block #90,888,348

17 transactions · 17 stateful · 2026-07-27 22:15:21 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.18

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,888,348  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x11b69a7e…334e

0x01bff4…1071

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x7aad02c6…b979

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x53ca1284…cb2c

0x34b655…2a6f

6 touches
3 conflicts

0x51a9172b…0723

0x851145…3f07

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: 0x01bff417…bc1071

6 conflicts on slot 0x11b69a7ea1…83334e

← previous block·next block →recent activity