← previous blocknext block →recent activity

Analyzing

Block #90,851,089

12 transactions · 11 stateful · 2026-07-27 19:07:52 UTC

Parallelism

67/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,851,089  ·  12 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

0x4b8d4ffe…0dba

0x34b655…2a6f

4 touches
1 conflict

0x7d6b9af1…9a38

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xda27c764…7fab

0x34b655…2a6f

4 touches
1 conflict

0x3f5831e5…02b2

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x0c376bba…95b1

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x4b8d4ffe42…8e0dba

← previous block·next block →recent activity