← previous blocknext block →recent activity

Analyzing

Block #90,960,792

16 transactions · 15 stateful · 2026-07-28 04:19:45 UTC

Parallelism

44/100

Blocked

67%

Avg conflicts / tx

2.44

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #90,960,792  ·  16 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xbde524f4…43bf

0x34b655…2a6f

18 touches
36 conflicts

0x705ab4ae…0162

0x34b655…2a6f

18 touches
36 conflicts

0xc824469a…6425

0x34b655…2a6f

18 touches
36 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

14 touches
21 conflicts

0x4ded138a…9497

0x34b655…2a6f

13 touches
21 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x879709ac…03bf

0x34b655…2a6f

5 touches
3 conflicts

0x78ffc631…fbae

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

36 conflicts on slot 0xbde524f475…b143bf

← previous block·next block →recent activity