← previous blocknext block →recent activity

Analyzing

Block #90,977,269

18 transactions · 18 stateful · 2026-07-28 05:42:39 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

0.61

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,977,269  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x3be75497…9a3c

0x34b655…2a6f

4 touches
1 conflict

0x424934c8…f2f1

0x34b655…2a6f

4 touches
1 conflict

0x62d6e82b…a750

0x34b655…2a6f

4 touches
1 conflict

0xafb8e71e…9285

0x34b655…2a6f

4 touches
1 conflict

0xbbeac3b7…c14b

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity