← previous blocknext block →recent activity

Analyzing

Block #90,644,827

14 transactions · 13 stateful · 2026-07-27 01:50:08 UTC

Parallelism

71/100

Blocked

46%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,644,827  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x013a6b08…d120

0x34b655…2a6f

4 touches
1 conflict

0x1bb624f3…c1b3

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x3de86e79…4d3d

0x34b655…2a6f

4 touches
1 conflict

0x4f2a18a7…1373

0x34b655…2a6f

4 touches
1 conflict

0x5abca0c6…2323

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 0xf3d10975b0…050d07

← previous block·next block →recent activity