← previous blocknext block →recent activity

Analyzing

Block #90,795,302

24 transactions · 24 stateful · 2026-07-27 14:27:09 UTC

Parallelism

63/100

Blocked

46%

Avg conflicts / tx

2.25

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #90,795,302  ·  24 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x6fe7d366…78ff

0x34b655…2a6f

16 touches
28 conflicts

0x00000000…00c9

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

8 touches
6 conflicts

0xf3383813…4a0c

0x34b655…2a6f

8 touches
6 conflicts

0x24eaf46d…8c2e

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x6a10a152…a08f

0x34b655…2a6f

6 touches
3 conflicts

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

28 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity