← previous blocknext block →recent activity

Analyzing

Block #90,771,609

29 transactions · 26 stateful · 2026-07-27 12:27:55 UTC

Parallelism

69/100

Blocked

54%

Avg conflicts / tx

1.45

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #90,771,609  ·  29 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

0xb35593a1…bfca

0x34b655…2a6f

18 touches
36 conflicts

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

14 touches
21 conflicts

0xa3f095f5…bd87

0x34b655…2a6f

8 touches
6 conflicts

0x4a39a2a4…857b

0x34b655…2a6f

6 touches
3 conflicts

0xb839a1e8…22b3

0x34b655…2a6f

6 touches
3 conflicts

0xfaf89f45…ced6

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

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

36 conflicts on slot 0xb35593a1a6…f7bfca

← previous block·next block →recent activity