← previous blocknext block →recent activity

Analyzing

Block #91,110,647

22 transactions · 21 stateful · 2026-07-28 16:54:36 UTC

Parallelism

77/100

Blocked

43%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,110,647  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2d651956…12e8

0x34b655…2a6f

4 touches
1 conflict

0x39fb42f2…35f2

0x34b655…2a6f

4 touches
1 conflict

0x5fab7fbe…1ce5

0x34b655…2a6f

4 touches
1 conflict

0x8252706a…7ca5

0x34b655…2a6f

4 touches
1 conflict

0x9c574ff9…2fb8

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity