← previous blocknext block →recent activity

Analyzing

Block #90,681,157

17 transactions · 15 stateful · 2026-07-27 04:52:55 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,681,157  ·  17 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

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x7032dc14…49ea

0x34b655…2a6f

4 touches
1 conflict

0x711ceb8d…5202

0x34b655…2a6f

4 touches
1 conflict

0x79871d6f…db7a

0x34b655…2a6f

4 touches
1 conflict

0x818b0b44…ff6f

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity