← previous blocknext block →recent activity

Analyzing

Block #90,233,873

19 transactions · 19 stateful · 2026-07-25 15:07:55 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

1.16

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,233,873  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xcc58c80b…ff79

0x34b655…2a6f

6 touches
3 conflicts

0xbb4fd99a…afa6

0x34b655…2a6f

6 touches
3 conflicts

0x1bb99bba…2911

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xbf68b5d2…0eba

0x34b655…2a6f

6 touches
3 conflicts

0xc857b971…0bcf

0x34b655…2a6f

6 touches
3 conflicts

0x99701186…1cbf

0x34b655…2a6f

6 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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity