← previous blocknext block →recent activity

Analyzing

Block #90,969,762

20 transactions · 20 stateful · 2026-07-28 05:04:54 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,969,762  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

10 touches
10 conflicts

0xafb8e71e…9285

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x1c8753e8…d214

0x34b655…2a6f

4 touches
1 conflict

0x34d95d94…3a16

0x34b655…2a6f

4 touches
1 conflict

0x424934c8…f2f1

0x34b655…2a6f

4 touches
1 conflict

0x442e26a3…e968

0x34b655…2a6f

4 touches
1 conflict

0x45b3c66c…b788

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity