← previous blocknext block →recent activity

Analyzing

Block #90,804,974

24 transactions · 23 stateful · 2026-07-27 15:15:49 UTC

Parallelism

71/100

Blocked

39%

Avg conflicts / tx

0.67

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,804,974  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xa429f7bc…88be

0x34b655…2a6f

8 touches
6 conflicts

0xcdc1731c…b91a

0x34b655…2a6f

6 touches
3 conflicts

0xabd0bcfc…64e2

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5388bf7d…df61

0x34b655…2a6f

4 touches
1 conflict

0x6f132c01…cdcc

0x34b655…2a6f

4 touches
1 conflict

0x7d6b9af1…9a38

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 0xa429f7bcd3…5788be

← previous block·next block →recent activity