← previous blocknext block →recent activity

Analyzing

Block #90,893,280

27 transactions · 21 stateful · 2026-07-27 22:40:10 UTC

Parallelism

67/100

Blocked

43%

Avg conflicts / tx

1

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #90,893,280  ·  27 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x5c16527f…628c

0x34b655…2a6f

8 touches
6 conflicts

0x0bd95eb4…e562

0x34b655…2a6f

6 touches
3 conflicts

0x4f8a11e8…ae2d

0x34b655…2a6f

6 touches
3 conflicts

0x0b34a794…400b

0x34b655…2a6f

6 touches
3 conflicts

0x6f5e7a23…6c6f

0x34b655…2a6f

6 touches
3 conflicts

0x96dd83e6…a507

0x34b655…2a6f

6 touches
3 conflicts

0xc44901fe…0fef

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity