← previous blocknext block →recent activity

Analyzing

Block #90,945,184

19 transactions · 19 stateful · 2026-07-28 03:01:16 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,945,184  ·  19 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

8 touches
6 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

6 touches
3 conflicts

0x1f396cee…862f

0x34b655…2a6f

6 touches
3 conflicts

0x6ac29cfd…136d

0x34b655…2a6f

6 touches
3 conflicts

0xcc58c80b…ff79

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

6 touches
3 conflicts

0x90be031d…01c6

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