← previous blocknext block →recent activity

Analyzing

Block #90,977,134

14 transactions · 13 stateful · 2026-07-28 05:41:58 UTC

Parallelism

71/100

Blocked

31%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,977,134  ·  14 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

0x2181494a…83fb

0x34b655…2a6f

6 touches
3 conflicts

0xbbeac3b7…c14b

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc4dc32ca…83f9

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x222b1f4f…6466

0x34b655…2a6f

4 touches
1 conflict

0x25329a48…4e00

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 0x2181494a5e…3483fb

← previous block·next block →recent activity