← previous blocknext block →recent activity

Analyzing

Block #90,809,026

30 transactions · 28 stateful · 2026-07-27 15:36:12 UTC

Parallelism

63/100

Blocked

64%

Avg conflicts / tx

1.83

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #90,809,026  ·  30 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x6fe7d366…78ff

0x34b655…2a6f

16 touches
28 conflicts

0x4c188934…158e

0x34b655…2a6f

10 touches
10 conflicts

0x0d488000…3831

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x28c714d9…9438

0xa6afd3…d132

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004b

0x80c745…7210

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

28 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity