← previous blocknext block →recent activity

Analyzing

Block #90,642,846

19 transactions · 17 stateful · 2026-07-27 01:40:10 UTC

Parallelism

58/100

Blocked

53%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #90,642,846  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xbcbf5d09…8bac

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x6f63ff36…1f48

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6426

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x932a9590…0b19

0x34b655…2a6f

6 touches
3 conflicts

0xc6b604e6…5152

0x34b655…2a6f

6 touches
3 conflicts

0xd192f4ed…d7ec

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

15 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity