← previous blocknext block →recent activity

Analyzing

Block #90,395,909

16 transactions · 16 stateful · 2026-07-26 04:52:46 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,395,909  ·  16 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x10797f0b…439a

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x312e4698…54c0

0x34b655…2a6f

6 touches
3 conflicts

0x4334088a…a88c

0x34b655…2a6f

6 touches
3 conflicts

0x2170bea4…4723

0x34b655…2a6f

4 touches
1 conflict

0xd793c15e…7dba

0x34b655…2a6f

4 touches
1 conflict

0x3bb514bf…2967

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity