← previous blocknext block →recent activity

Analyzing

Block #90,604,282

13 transactions · 12 stateful · 2026-07-26 22:26:10 UTC

Parallelism

69/100

Blocked

42%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,604,282  ·  13 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xd800e635…b1d7

0x34b655…2a6f

6 touches
3 conflicts

0xec6f7545…d15b

0x34b655…2a6f

4 touches
1 conflict

0xef3f5637…f47c

0x34b655…2a6f

4 touches
1 conflict

0xf2f4727d…cdb7

0x34b655…2a6f

4 touches
1 conflict

0x5da59c2b…d7b2

0x34b655…2a6f

4 touches
1 conflict

0x5e2ea201…12de

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 0xc824469a90…af6425

← previous block·next block →recent activity