← previous blocknext block →recent activity

Analyzing

Block #90,866,041

7 transactions · 6 stateful · 2026-07-27 20:23:08 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,866,041  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x74f95963…01a2

0x34b655…2a6f

4 touches
1 conflict

0x03fb27fd…0c06

0x34b655…2a6f

2 touches
0 conflicts

0x0733be30…112f

0x34b655…2a6f

2 touches
0 conflicts

0x0e52d81f…461e

0x34b655…2a6f

2 touches
0 conflicts

0x1f6f8ff8…a5d4

0x34b655…2a6f

2 touches
0 conflicts

0x1f6f8ff8…a5d5

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity