← previous blocknext block →recent activity

Analyzing

Block #90,893,372

17 transactions · 16 stateful · 2026-07-27 22:40:37 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,893,372  ·  17 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x808129fc…f97d

0x34b655…2a6f

6 touches
3 conflicts

0x4f1ad4b4…e00a

0x34b655…2a6f

6 touches
3 conflicts

0x5c16527f…628c

0x34b655…2a6f

6 touches
3 conflicts

0xb566cc65…214d

0xa6afd3…d132

4 touches
1 conflict

0x05e1eba1…6491

0x34b655…2a6f

4 touches
1 conflict

0x29f56709…699b

0x34b655…2a6f

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity