← previous blocknext block →recent activity

Analyzing

Block #90,796,382

20 transactions · 18 stateful · 2026-07-27 14:32:35 UTC

Parallelism

45/100

Blocked

67%

Avg conflicts / tx

2.35

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #90,796,382  ·  20 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xbe54b7d5…1bda

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x1a5d321d…a474

0x34b655…2a6f

6 touches
3 conflicts

0x3ea25e92…a36d

0x34b655…2a6f

6 touches
3 conflicts

0x7a2c83a3…a29a

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

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