← previous blocknext block →recent activity

Analyzing

Block #90,811,395

25 transactions · 22 stateful · 2026-07-27 15:48:12 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.6

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,811,395  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x94bb14fe…8f47

0x34b655…2a6f

6 touches
3 conflicts

0xc6000ba5…8d65

0x34b655…2a6f

6 touches
3 conflicts

0xc6b9bb4b…145a

0x34b655…2a6f

6 touches
3 conflicts

0x41377979…0a18

0x34b655…2a6f

6 touches
3 conflicts

0xbadc08dd…cf76

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

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity