← previous blocknext block →recent activity

Analyzing

Block #90,999,995

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

Parallelism

81/100

Blocked

39%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,999,995  ·  21 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

0xc014bcf3…3ac7

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0006

0x7b9256…1fb2

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe3e6c02a…d3d4

0x34b655…2a6f

4 touches
1 conflict

0xf28a9fc2…05e4

0x34b655…2a6f

4 touches
1 conflict

0xe1f61186…e2f8

0x754704…b603

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

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 0xc014bcf38f…c73ac7

← previous block·next block →recent activity