← previous blocknext block →recent activity

Analyzing

Block #90,876,764

20 transactions · 19 stateful · 2026-07-27 21:17:05 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.9

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,876,764  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x002fed35…79fa

0x2a68ba…90c5

8 touches
6 conflicts

0x11b69a7e…334e

0x01bff4…1071

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xbd9e5b16…e3a0

0x851145…3f07

6 touches
3 conflicts

0x89999c15…fdac

0x34b655…2a6f

6 touches
3 conflicts

0xbb8dc535…4fe7

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641e

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

6 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity