← previous blocknext block →recent activity

Analyzing

Block #91,087,886

22 transactions · 21 stateful · 2026-07-28 15:00:04 UTC

Parallelism

68/100

Blocked

43%

Avg conflicts / tx

1.09

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,087,886  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xbde524f4…43bf

0x34b655…2a6f

14 touches
21 conflicts

0x4bc1abab…5874

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

12 touches
15 conflicts

0xf3d10975…0d07

0x34b655…2a6f

12 touches
15 conflicts

0xfcc138c5…e023

0x34b655…2a6f

8 touches
6 conflicts

0x760a6907…e4cf

0x34b655…2a6f

7 touches
6 conflicts

0xac01523f…8fe6

0x34b655…2a6f

5 touches
3 conflicts

0x806bf739…e950

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

21 conflicts on slot 0xbde524f475…b143bf

← previous block·next block →recent activity