← previous blocknext block →recent activity

Analyzing

Block #90,720,758

20 transactions · 19 stateful · 2026-07-27 08:12:07 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

1.15

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,720,758  ·  20 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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

6 touches
3 conflicts

0x007892de…5752

0x34b655…2a6f

6 touches
3 conflicts

0x28e32856…45f6

0x34b655…2a6f

6 touches
3 conflicts

0x43da11dc…5a2f

0x34b655…2a6f

6 touches
3 conflicts

0x6e5d7a21…b2fe

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x934da4f1…43a7

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity