← previous blocknext block →recent activity

Analyzing

Block #90,820,146

20 transactions · 17 stateful · 2026-07-27 16:32:14 UTC

Parallelism

70/100

Blocked

53%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,820,146  ·  20 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

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x0fffa5c0…a3a9

0xa6afd3…d132

4 touches
1 conflict

0x731f2745…9370

0xa6afd3…d132

4 touches
1 conflict

0x11b69a7e…334e

0x01bff4…1071

4 touches
1 conflict

0x0bd95eb4…e562

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 0x737acb7813…fafce8

← previous block·next block →recent activity