← previous blocknext block →recent activity

Analyzing

Block #90,643,030

21 transactions · 18 stateful · 2026-07-27 01:41:06 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

0.9

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,643,030  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x94ddea60…a24d

0x34b655…2a6f

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x2f68ff96…38a6

0x34b655…2a6f

6 touches
3 conflicts

0x3e30f1bf…6453

0x34b655…2a6f

5 touches
3 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

10 conflicts on slot 0x94ddea6064…31a24d

← previous block·next block →recent activity