← previous blocknext block →recent activity

Analyzing

Block #90,884,542

17 transactions · 16 stateful · 2026-07-27 21:56:12 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,884,542  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xcb10fd4e…6167

0x34b655…2a6f

6 touches
3 conflicts

0x0bd95eb4…e562

0x34b655…2a6f

6 touches
3 conflicts

0xddd7607e…9b4b

0x34b655…2a6f

6 touches
3 conflicts

0x5af10b50…8d5c

0x34b655…2a6f

4 touches
1 conflict

0x69a45f39…39aa

0x34b655…2a6f

4 touches
1 conflict

0x6f3ece6e…c36f

0x34b655…2a6f

4 touches
1 conflict

0x80404691…4a11

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity