← previous blocknext block →recent activity

Analyzing

Block #90,816,055

21 transactions · 19 stateful · 2026-07-27 16:11:39 UTC

Parallelism

71/100

Blocked

37%

Avg conflicts / tx

0.57

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,816,055  ·  21 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

0xa3f6f7c8…2436

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x428b6e5b…8909

0x34b655…2a6f

4 touches
1 conflict

0x5e47cbde…9659

0x34b655…2a6f

4 touches
1 conflict

0xb476ee35…c627

0xa6afd3…d132

4 touches
1 conflict

0x228d47a0…0efa

0x34b655…2a6f

4 touches
1 conflict

0x31c8e43e…61ba

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 0xa3f6f7c8bd…f22436

← previous block·next block →recent activity