← previous blocknext block →recent activity

Analyzing

Block #90,537,997

21 transactions · 20 stateful · 2026-07-26 16:52:43 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,537,997  ·  21 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

0xea02471d…1542

0x34b655…2a6f

12 touches
15 conflicts

0xf3d10975…0d07

0x34b655…2a6f

12 touches
15 conflicts

0x4bc1abab…5874

0x34b655…2a6f

12 touches
15 conflicts

0xbde524f4…43bf

0x34b655…2a6f

12 touches
15 conflicts

0xe2b888e1…9374

0x34b655…2a6f

9 touches
10 conflicts

0x033cf007…136d

0x34b655…2a6f

6 touches
3 conflicts

0x66bdb4c2…7ea6

0x34b655…2a6f

6 touches
3 conflicts

0xf7ee61f5…f81a

0x34b655…2a6f

5 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

15 conflicts on slot 0xea02471df2…601542

← previous block·next block →recent activity