← previous blocknext block →recent activity

Analyzing

Block #90,850,728

17 transactions · 17 stateful · 2026-07-27 19:06:04 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.88

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,850,728  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xa33ecf51…7216

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x20067ecb…0e41

0x34b655…2a6f

4 touches
1 conflict

0x344bc09a…942f

0x34b655…2a6f

4 touches
1 conflict

0x46483cb1…e7ca

0x34b655…2a6f

4 touches
1 conflict

0x4b375a43…c6ff

0x34b655…2a6f

4 touches
1 conflict

0x4d3a9de0…7c14

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 0xa33ecf515f…b67216

← previous block·next block →recent activity