← previous blocknext block →recent activity

Analyzing

Block #90,784,576

22 transactions · 18 stateful · 2026-07-27 13:33:09 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,784,576  ·  22 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

0xa6b89ebb…a66e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x17e90565…d957

0xa6afd3…d132

4 touches
1 conflict

0xd0eb199c…dcfc

0x34b655…2a6f

4 touches
1 conflict

0xd93edb3f…94ec

0x34b655…2a6f

4 touches
1 conflict

0xd9a771df…a27b

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x48cba2…b48b

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 0xa6b89ebbaf…5fa66e

← previous block·next block →recent activity