← previous blocknext block →recent activity

Analyzing

Block #90,851,083

18 transactions · 18 stateful · 2026-07-27 19:07:51 UTC

Parallelism

72/100

Blocked

39%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,851,083  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xb069d064…7ba6

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x3055b4d0…81c0

0x34b655…2a6f

4 touches
1 conflict

0x6f132c01…cdcc

0x34b655…2a6f

4 touches
1 conflict

0x74f95963…01a2

0x34b655…2a6f

4 touches
1 conflict

0xa35509fa…5cb3

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 0xb069d0640f…427ba6

← previous block·next block →recent activity