← previous blocknext block →recent activity

Analyzing

Block #90,794,198

21 transactions · 16 stateful · 2026-07-27 14:21:35 UTC

Parallelism

86/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,794,198  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xfb31d278…9107

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x5d46e6a0…5ed9

0x40c49f…2af0

4 touches
1 conflict

0x76d1e78d…7877

0x40c49f…2af0

4 touches
1 conflict

0x00000000…0002

0x48cba2…b48b

4 touches
1 conflict

0x482471ad…122f

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

← previous block·next block →recent activity