← previous blocknext block →recent activity

Analyzing

Block #90,792,268

18 transactions · 16 stateful · 2026-07-27 14:11:53 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,792,268  ·  18 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

0xa6b89ebb…a66e

0x34b655…2a6f

6 touches
3 conflicts

0x634dddde…2af8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x93b6fab0…09d6

0x34b655…2a6f

6 touches
3 conflicts

0x62d6e82b…a750

0x34b655…2a6f

4 touches
1 conflict

0x62dbeb4d…a388

0x34b655…2a6f

4 touches
1 conflict

0x6aa0302c…bc76

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xa6b89ebbaf…5fa66e

← previous block·next block →recent activity