← previous blocknext block →recent activity

Analyzing

Block #90,539,784

32 transactions · 23 stateful · 2026-07-26 17:01:42 UTC

Parallelism

84/100

Blocked

26%

Avg conflicts / tx

0.41

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,539,784  ·  32 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xf9ac650a…d82d

0x34b655…2a6f

6 touches
3 conflicts

0x680fdd59…e84d

0x34b655…2a6f

6 touches
3 conflicts

0x38d548ea…baf6

0x34b655…2a6f

4 touches
1 conflict

0x3e43fb5b…c0ff

0x34b655…2a6f

4 touches
1 conflict

0x63c900f4…2600

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x6b47245e…a342

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

← previous block·next block →recent activity