← previous blocknext block →recent activity

Analyzing

Block #90,796,156

23 transactions · 17 stateful · 2026-07-27 14:31:26 UTC

Parallelism

83/100

Blocked

41%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,796,156  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x76d1e78d…7877

0x40c49f…2af0

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x1a5d321d…a474

0x34b655…2a6f

4 touches
1 conflict

0x45ef9175…5ab2

0x34b655…2a6f

4 touches
1 conflict

0xbe54b7d5…1bda

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x731f2745…9370

0xa6afd3…d132

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: 0x40c49f17…d22af0

3 conflicts on slot 0x76d1e78d12…117877

← previous block·next block →recent activity