← previous blocknext block →recent activity

Analyzing

Block #90,534,942

18 transactions · 16 stateful · 2026-07-26 16:37:21 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,534,942  ·  18 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

0xda27c764…7fab

0x34b655…2a6f

8 touches
6 conflicts

0x53117088…1a0c

0x34b655…2a6f

8 touches
6 conflicts

0x1e56f6b6…5940

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xcb0221be…c2b3

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x80398c66…f3cc

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

6 conflicts on slot 0xda27c76455…2e7fab

← previous block·next block →recent activity