← previous blocknext block →recent activity

Analyzing

Block #90,791,242

23 transactions · 21 stateful · 2026-07-27 14:06:43 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,791,242  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x93b6fab0…09d6

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x3d222a5e…ecac

0x34b655…2a6f

4 touches
1 conflict

0x516f4295…fad1

0x34b655…2a6f

4 touches
1 conflict

0x5d94234c…b05d

0x34b655…2a6f

4 touches
1 conflict

0x5e3014f0…b4e1

0x34b655…2a6f

4 touches
1 conflict

0xa4041c86…a637

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x92385428ad…dc6941

← previous block·next block →recent activity